Request an upload URL using the SP-API Feeds API createFeedDocument endpoint specifying the content type for the override feed format
Upload the override data file to the presigned S3 URL returned by createFeedDocument using a PUT request with the exact content type specified
Create the feed submission by calling the createFeed endpoint with the feed type, marketplace IDs, and the feed document ID obtained from the upload step
Poll the getFeed endpoint using the feed ID until the processingStatus transitions to DONE or FATAL, implementing exponential backoff between polls to avoid throttling
On completion, retrieve the feed result document URL from the getFeed response, download and decrypt the result report, and parse per-ASIN success and error records
For ASINs with errors, classify the error type: system errors are retryable, data validation errors require correction of the override attributes before resubmission
Known gotchas
The presigned S3 upload URL from createFeedDocument expires in a short window; upload the feed file immediately after receiving the URL and do not cache it for later use
Amazon feed processing is asynchronous and can take hours for large submissions; do not re-submit the same feed if the first is still processing, as duplicate submissions create conflicting override records
Regional overrides must be submitted to each targeted marketplace separately; a feed submitted to one marketplace ID does not propagate overrides to other regional marketplaces even within the same selling account
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp