feeds_getFeed

Get Amazon feed processing status (getFeed).

readAmazon Seller (SP-API)sp.feeds_2021-06-30

Whenever Amazon has a result document for the feed, it is auto-fetched + decoded (getFeedDocument is folded in — the server resolves resultFeedDocumentId, downloads the presigned URL, gunzips, and decodes to text). Amazon attaches a result document to FATAL feeds too, not only DONE ones. Amazon SP-API · getFeed · GET /feeds/2021-06-30/feeds/{feedId} Amazon SP-API · getFeedDocument · GET /feeds/2021-06-30/documents/{feedDocumentId} Call this repeatedly to poll until processingStatus is terminal. Feeds typically complete within 1–5 minutes. Terminal vs retryable: 'DONE', 'FATAL' and 'CANCELLED' are terminal — polling again can never change them. Only 'IN_QUEUE' / 'IN_PROGRESS' are worth another call.

Call it

In an AI client (MCP)

tools/call
{
  "name": "feeds_getFeed",
  "arguments": {
    "store": "myStore-US",
    "feedId": "<feedId>"
  }
}

From code (Tool API)

curl -X POST https://api.sellersheetai.com/api/v1/tools/feeds_getFeed \
  -H "Authorization: Bearer $SELLERSHEET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"store":"myStore-US","feedId":"<feedId>"}'
Early access — the Tool API is open on request, contact us.

Arguments

NameTypeDescription
storerequiredstringthe store ref `<store>-<CC>` (name-country, e.g. 'myStore-US') — one of get_user_context's store_refs, verbatim.
feedIdrequiredstringAmazon feed ID returned by feeds_createFeed.

Result

Every tool answers {notification, data, human_action}; data carries:

  • data.feedId — same as input.
  • data.processingStatus — Amazon enum 'IN_QUEUE' | 'IN_PROGRESS' | 'DONE' | 'CANCELLED' | 'FATAL', plus the SellerSheet-synthetic 'NOT_FOUND' (returned as a warning when Amazon has no such feed for this store).
  • data.resultFeedDocumentId — Amazon's result-document id, whenever Amazon returned one (DONE and FATAL feeds both carry one).
  • data.document — (whenever Amazon has a result document — DONE or FATAL) Decoded string content of the feed processing report. For a JSON listings feed a JSON report {header, summary {messagesProcessed, messagesAccepted, messagesInvalid, errors, warnings}, issues [{messageId, code, severity, message, attributeName}]} — messageId n is the n-th message sent. For XML feeds an XML summary with counts of messages processed, warnings, and errors. On FATAL it says why Amazon aborted.

Workflow

  • 1. Read data.processingStatus. 2. DONE: read data.document (the processing report) and report each message's issues. 3. IN_QUEUE or IN_PROGRESS: wait 2–5 minutes, then call again. 4. CANCELLED or FATAL: relay the reason; the feed was not applied. 5. NOT_FOUND: the feedId is invalid or was submitted to a different store.

Params (Amazon schema; getFeed)

feedId*: string

Params (Amazon schema; getFeedDocument)

feedDocumentId*: string
enableContentEncodingUrlHeader: boolean

On this page

Actions

View as Markdown

Ask an assistant

Ask ChatGPTAsk Claude