Amazon FBA label API for seller and warehouse backends
Render Amazon FBA-style product, carton, and shipment label PDFs from seller or warehouse data with vector barcodes and template output.
/api/v1/pdf/render Render product, carton, or shipment label PDFs for Amazon FBA preparation workflows after your seller, prep, or warehouse system has determined the correct identifiers, barcode payloads, and label rules.
When to use this API
- Your system already has the FNSKU, carton, shipment, or prep-service label data.
- You need vector barcode labels as PDF output for seller or warehouse print stations.
- You want repeated label layouts to become Template Render contracts.
- You need deterministic reprints for prep, audit, or exception handling.
What it does not replace
- You need an official Amazon integration, app, or SP-API connector from gPdf.
- You need Amazon to certify the label through gPdf.
- You need inventory, listing, or shipment-plan management.
Which endpoint to call
/api/v1/pdf/render
JSON Render is the default path for this workflow.
/api/v1/template-render
Use this when the workflow needs the related API path, template contract, or capabilities lookup.
Minimal request
POST /api/v1/pdf/render - product label with an FNSKU-style barcode payload.
{
"pages": [
{
"width": 70,
"height": 35,
"elements": [
{
"type": "text",
"x": 4,
"y": 4,
"content": "FNSKU X00ABC1234",
"style": { "font_size": 8, "font_family": "NotoSans-Regular" }
},
{
"type": "barcode",
"format": "code128",
"content": "X00ABC1234",
"x": 4,
"y": 12,
"width": 60,
"height": 12,
"barcode_text": { "enabled": true, "position": "bottom" }
},
{
"type": "text",
"x": 4,
"y": 29,
"content": "SKU: ACME-FILTER-01",
"style": { "font_size": 6, "font_family": "NotoSans-Regular" }
}
]
}
]
}
What gPdf handles
- Label-sized PDF rendering from JSON Render payloads.
- Vector barcodes, text, SKU blocks, boxes, and template binding.
- Repeated label output through Template Render.
- PDF responses for print stations, seller tools, or warehouse workflows.
What your system owns
- Amazon account integration, SP-API calls, shipment plan data, FNSKU values, and marketplace rules.
- Correct barcode payloads, label dimensions, product data, and scan acceptance.
- Seller UX, prep workflow, storage, and reprint authorization.
Production checklist
- Confirm the active marketplace and fulfillment requirements before rendering.
- Validate barcode payloads and physical print quality on production label stock.
- Keep Amazon integration and credential handling outside gPdf.
- Store the source label data so reprints are deterministic.
- Move approved layouts to Template Render for print-station integrations.
Claim boundaries
- gPdf is not an official Amazon app or SP-API connector.
- gPdf renders PDFs; Amazon compliance and seller workflow rules remain yours.
- Do not treat PDF rendering as Amazon label certification.
FBA labels are data-driven PDF labels
Amazon FBA preparation workflows often need product, carton, or shipment labels. The rendering problem is straightforward: your system supplies the identifiers and label rules, and gPdf renders the PDF.
Keep marketplace integration separate from rendering. Fetch or compute the right identifiers in your seller or warehouse system, then call gPdf with the final label payload.
FAQ
- Is gPdf an official Amazon FBA app?
- No. A seller, prep, or warehouse backend can call gPdf, but gPdf does not claim an official Amazon app or SP-API integration.
- Can gPdf render FNSKU labels?
- gPdf can render PDF labels with barcode elements. Your system owns the FNSKU value, label rules, and Amazon workflow.
- Should FBA labels use templates?
- Use JSON Render while testing coordinates. Use Template Render after the label design and field contract are approved.
- Does gPdf certify labels for Amazon?
- No. Print quality, scan acceptance, and marketplace compliance remain your responsibility.