API Integration Setup: Days (middleware) to weeks (own approval)

Amazon × PrintHub — three realistic paths to POD fulfillment

Amazon's SP-API only delivers shipping addresses and personalization data with approved "Restricted Roles" — the process is demanding but doable. We walk you through the three paths: middleware, Reports API and your own approval.

Free consultation call Go to API documentation

Overview

Amazon treats shipping data and personalization info (BuyerCustomizedInfo) as "Personally Identifiable Information" (PII). Accessing that data requires an approved Restricted Role — in particular "Direct-to-Consumer Shipping". The same is true for self-authorized private apps: the architecture review is waived, but role approval is still mandatory. There are three workable paths which we recommend depending on volume and setup.

Benefits

Why Amazon with PrintHub?

Sell personalized products on Amazon

Via Amazon Custom, Brand Registry or your own listing with an engraving service — fulfillment via PrintHub without holding stock. Personalization comes either from BuyerCustomizedInfo or from variations.

Three viable paths, no vendor lock-in

You choose: middleware like Billbee or ShipStation (fast, monthly fee), the Reports API with limited PII needs, or the Direct-to-Consumer Shipping role at Amazon. We support all three options.

SFP-compatible for the Prime badge

DHL standard shipping in 1–2 business days out of Hamburg meets the Seller Fulfilled Prime SLAs for Germany and the core EU markets.

Compatible with Orders API v2026-01-01

In Amazon's new Orders API version, Restricted Data Tokens (RDT) are no longer required — access is role-based. This removes a significant amount of technical overhead. Role approval is still mandatory, though.

Setup

Live in Days (middleware) to weeks (own approval)

Step by step — from zero to your first automated order.

  1. 01

    Path 1: middleware with existing PII access (recommended for the start)

    Tools like Billbee, ShipStation, Sellercloud or Linnworks are already certified by Amazon as third parties authorized for PII access. You connect Amazon Seller Central to the middleware and it forwards order data (including customization) to our POST /api/orders via webhook or API. Setup takes roughly one day, ongoing fee depending on the provider.

  2. 02

    Path 2: Reports API for limited use cases

    For standard products without personalization the report GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_GENERAL is often enough — but even that contains PII and requires a Restricted Role. For Amazon Custom, GET_AMAZON_CUSTOM_PRODUCT_REPORT can partially deliver customization data. A case-by-case check is required.

  3. 03

    Path 3: apply for the Direct-to-Consumer Shipping role at Amazon

    Long-term the cleanest path for higher volumes. In your developer profile you apply for the "Direct-to-Consumer Shipping" Restricted Role with a detailed data protection plan (GDPR, encryption, retention periods, access controls). References to ISO 27001, SOC 2 or NIST improve your chances. The process typically takes 4–12 weeks including back-and-forth and iterative follow-ups.

  4. 04

    Create a PrintHub API key and set up mapping

    Regardless of the chosen path: generate a pk_live_ key in the partner dashboard, configure a webhook URL for status updates (order.shipped, order.error) and map Amazon ASINs or SKUs to PrintHub products.

  5. 05

    Tracking push-back to Amazon

    After shipment PrintHub sends an order.shipped webhook. Your middleware calls submitFeed (FulfillmentShipmentFeed) on the SP-API. The write itself is less restricted than reading PII — normal app access is usually enough for feed submission.

Features

What this integration can do

  • Three documented integration paths (middleware / reports / own role approval)
  • Compatible with Billbee, ShipStation, Sellercloud, Linnworks, Customily
  • Orders API v2026-01-01 ready — no RDT token handling
  • Support drafting the data protection plan for role approval
  • SFP-ready with DHL SLA compliance (1–2 business days in DE)
  • Returns handled via Amazon's standard return flow
Code sample

Get started right away

Example for path 1: the middleware (Billbee) calls the PrintHub API with ready-to-use order data — you don't have to apply for PII access at Amazon yourself.

javascript api.print-hub.com 
// Webhook-Handler in deiner Middleware (Billbee, ShipStation, eigene Lambda)
// Die Middleware hat bereits Amazon-PII-Zugriff — wir bekommen nur fertige Bestellungen

export async function handleAmazonOrder(billbeeOrder) {
  await fetch('https://api.print-hub.com/api/orders', {
    method: 'POST',
    headers: {
      'X-API-Key': process.env.PRINTHUB_KEY,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      external_id: billbeeOrder.orderNumber,    // Amazon-Order-ID
      customer: {
        name: billbeeOrder.buyer.name,          // Kommt aus Billbee, nicht direkt aus SP-API
        street: billbeeOrder.shipping.street,
        zip: billbeeOrder.shipping.zip,
        city: billbeeOrder.shipping.city,
        country: billbeeOrder.shipping.country,
      },
      items: billbeeOrder.items.map((item) => ({
        product_id: mapAsinToPrinthub(item.asin),
        quantity: item.quantity,
        properties: {
          engraving: item.customization,        // BuyerCustomizedInfo via Middleware
        },
      })),
    }),
  });
}
Frequently asked

What partners often ask us

Can I skip the PII Restricted Role at Amazon?
Not entirely, but you can delegate it: PII-certified middleware like Billbee or ShipStation already holds the approval and hands you the finished order data — you never call the SP-API with PII yourself. Self-authorized private apps only skip the architecture review, not the role approval for PII access.
How do I access personalization data (BuyerCustomizedInfo)?
BuyerCustomizedInfo is classified as PII by Amazon and only delivered with an approved Restricted Role. Three practical paths: (1) middleware like Customily or Billbee that already have the access, (2) check GET_AMAZON_CUSTOM_PRODUCT_REPORT case by case, (3) apply for your own approval — see the next question.
How does the approval for Direct-to-Consumer Shipping work?
You update your developer profile in Seller Central with a use case ("personalized production, direct shipping to end customers"), a detailed data protection plan (GDPR, encryption, retention periods, access controls) and references to ISO 27001, SOC 2 or NIST standards. Amazon reviews for 4–12 weeks, often with follow-up questions. We help draft it — bring it up in the consultation call.
What does the new Orders API v2026-01-01 bring?
In the new version the Restricted Data Token (RDT) is no longer required — access is purely role-based. That saves one technical extra step per call. The Restricted Role itself (Direct-to-Consumer Shipping) is still required for PII data.
Do I need Amazon Seller Central?
Yes, an active Seller Central account is required. Path 1 (middleware) is enough. Path 3 (own approval) additionally needs a developer account in the developer center and the approved Restricted Roles.
Can I offer Prime shipping (SFP)?
Yes. We meet the SFP SLAs for Germany — production and DHL shipping within 1–2 business days. Amazon's Prime badge depends on your individual SFP approval.
How do returns work?
Via Amazon's standard return flow. The customer ships to your returns address (either your warehouse or PrintHub Hamburg). On production defects we replace free of charge.

Ready to connect Amazon with PrintHub?

In a 30-minute call we go over your setup, catalog and volume — and send you out with a concrete roadmap.

Start now View product catalog

Further reading

API documentation Shopify integration Direct API usage Book a consultation