aplusContent_getContentDocument
Get an A+ Content document.
readAmazon Seller (SP-API)sp.aplusContent_2020-11-01
``includedDataSet`` selects which data types Amazon returns (full contents and/or just metadata). Amazon SP-API · getContentDocument · GET /aplus/2020-11-01/contentDocuments/{contentReferenceKey} Use this to inspect an existing document before updating or to audit content.
Call it
In an AI client (MCP)
{
"name": "aplusContent_getContentDocument",
"arguments": {
"store": "myStore-US",
"contentReferenceKey": "<contentReferenceKey>"
}
}From code (Tool API)
curl -X POST https://api.sellersheetai.com/api/v1/tools/aplusContent_getContentDocument \
-H "Authorization: Bearer $SELLERSHEET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"store":"myStore-US","contentReferenceKey":"<contentReferenceKey>"}'Early access — the Tool API is open on request, contact us.
Arguments
| Name | Type | Description |
|---|---|---|
storerequired | string | the store ref `<store>-<CC>` (name-country, e.g. 'myStore-US') — one of get_user_context's store_refs, verbatim. |
contentReferenceKeyrequired | string | the A+ content document key (from aplusContent_searchContentDocuments). |
includedDataSet | string[] | which A+ data types to return, any subset: CONTENTS is the full content document (modules + text + images), METADATA the document's metadata only (name/status/badges/updateTime). Amazon requires this query param; the server sends ['CONTENTS'] when omitted. Pass ['CONTENTS','METADATA'] for both, or ['METADATA'] for a lightweight metadata-only fetch.CONTENTSMETADATA |
Result
Every tool answers {notification, data, human_action}; data carries:
data.contentReferenceKey— same as input.data.contentDocument— the contentDocument itself — the server unwraps Amazon's GET envelope, so this dict can be passed straight back into ``aplusContent_updateContentDocument``. Present when CONTENTS was requested (None for a METADATA-only fetch). Fields: - name: content name (maxLength 100) - contentType: 'EBC' (Seller Central A+ — what seller accounts get) or 'EMC' (Vendor Central A+) - contentSubType: optional special-purpose subtype string (often absent) - locale: IETF language tag, HYPHENATED — pattern ^[a-z]{2,}-[A-Z0-9]{2,}$ (e.g. 'en-US', 'en-GB', 'de-DE', 'zh-CN'). Underscores are rejected. - contentModuleList: 1–100 module dicts, each with: - contentModuleType: module type string (e.g. 'STANDARD_HEADER_IMAGE_TEXT') - [module-specific key]: module data with images and textdata.contentMetadata— (if present, i.e. when METADATA was requested) name/status/badgeSet/marketplaceId/updateTime.data.warnings— (if present) Amazon advisory messages ({code, message, details}).
Gotchas
- A PREMIUM A+ document can fail with 400 "Unsupported content module type" — read its metadata from aplusContent_searchContentDocuments instead.