Deploy a product listing to Amazon (async)
POST/v2/amazon/deploy-products
Amazon Listings API is async; this endpoint accepts the listing and returns HTTP 202 Accepted with Location + Retry-After headers following RFC 7231 long-running-operation pattern. Partners poll GET /v1/report-product-deploy/{request_deploy_id} to observe status transitions Initial → Open → InProgress → Completed|Failed.
Attribute validation: amazon_attributes is pass-through to the Amazon Listings API 2021-08-01 — Dodgeprint does not maintain a per-product_type whitelist. The only server-side checks are: (1) the key exists, (2) amazon_attributes.fulfillment_availability.lead_time_to_ship_max_days + fulfillment_channel_code are present (required by the payload factory). Any other Amazon constraint (required fields per product_type, enum values, schema) is validated by Amazon at listing acceptance time and surfaces via the deploy-status poll. Consult Amazon SP-API GET /definitions/2020-09-01/productTypes/{productType} for authoritative per-type schemas.
Request
Responses
- 202
- 400
- 401
- 403
- 422
Deploy accepted and running asynchronously. Poll the URL in the Location header (or build /v1/report-product-deploy/{request_deploy_id}) every Retry-After seconds until status is Completed or Failed.
Response Headers
Polling endpoint, e.g. /api/v1/report-product-deploy/185901
Recommended polling interval in seconds (default 5)
Business-logic validation failed (e.g. Amazon prerequisites missing)
Unauthenticated
Invalid workspace session
Body validation failed (missing required fields, invalid shape)