Amazon Seller Central Integration

Learn how to publish AI Tools that connect to buyers' Amazon Seller Central accounts via the Selling Partner API (SP-API).

This integration lets your AI Agent automation read product listings, fetch order metrics, analyze catalog data, manage feeds, and update A+ content. SellerShorts makes SP-API calls on behalf of buyers through your AI Agent.

Security & Privacy: All API calls are made through SellerShorts' secure infrastructure. Sellers never have direct access to buyer Amazon Seller Central accounts.

Access is scoped to the specific order and capabilities defined for the AI Tool. All tokens are encrypted at rest (AES-256-GCM) and signed with AWS SigV4 on every SP-API call.

🔒 Token & Credential Handling

AI Tool builders never receive Amazon tokens, credentials, or login information. They only receive a SellerShorts job_token.
SellerShorts stores all Amazon tokens encrypted and signs every API call before forwarding to Amazon on the buyer's behalf.
Buyers can revoke access anytime from Connected Accounts or directly from Amazon.

This architecture complies with Amazon's Data Protection Policy (DPP) and Acceptable Use Policy (AUP).

Overview

When you publish an AI Tool that requires Amazon Seller Central access, buyers connect their own Amazon Seller Central accounts when they run your AI Tool.

Your AI Agent automation receives a secure job_token that allows it to request SP-API calls through SellerShorts on the buyer's behalf.

All 10 available capabilities are automatically enabled when you select Amazon Seller Central. No additional configuration needed.

End-to-end flow (at a glance)

Creator setup: define required inputs and select Amazon Seller Central in the Inputs step.Inputs guide
Buyer run: buyer fills inputs and connects their Amazon Seller Central account; SellerShorts issues a job_token.
Agent execution: your automation uses the job_token to call SellerShorts → Amazon SP-API.
Processing: fetch data, analyze, and generate the requested output.
Return results: POST back to your callback/webhook URL with the output.Callback guide

💡 How it works

You select Amazon Seller Central as a required connection in the Inputs step
11 SP-API capabilities are automatically enabled for your AI Agent (connect, products, catalog, feeds, orders, analytics, listings.upload_feed, listings.a_plus_generate, messaging.request_review, account_health.fetch). 3 additional Listings Items API verbs (listings.get, listings.update, listings.update_images) are available on opt-in via the wizard's "Post to Amazon (Optional)" section.
When a buyer runs your AI Tool, they connect their Amazon Seller Central account via OAuth
Your webhook receives a job_token in the payload
Your automation uses this token to call SellerShorts API endpoints for SP-API operations
SellerShorts signs every request with AWS SigV4 and forwards to Amazon SP-API on the buyer's behalf

Important: Primary User Requirement

⚠️ Sellers must be the PRIMARY user

Per Amazon's official policy, the seller must be logged into Amazon Seller Central as the PRIMARY user (account owner) with the registered primary email address before they authorize your AI Tool. Secondary users, even those with admin privileges, cannot complete the authorization.

If a buyer sees a blank consent page after picking a marketplace, this is the most common reason. Instruct them to log out of Seller Central, log back in as the primary user, then retry the connection.

Important: What SellerShorts' Amazon SP-API App Is (And Isn't) Approved For

🔒 Amazon-approved scope (production-tier SP-API app: sellershorts_prod)

SellerShorts is registered with Amazon as a Solution Provider for the Selling Partner API. The approval scope is fixed and constrains what your AI Tool can do via the broker. Please design within these limits:

Approved business entity:

Sellers only. SellerShorts' SP-API app supports Amazon Sellers (third-party Marketplace sellers). It does not support Amazon Business or Vendors (1P). AI Tools intended for Vendor or Amazon Business workflows cannot be built on the SP-API integration today.

SP-API roles requested at OAuth time:

Product Listing (covers listings.upload_feed, listings.a_plus_generate, listings.get, listings.update, listings.update_images, catalog.search, products.list, products.detail). Per Amazon's role description: "Create and manage product listings, including A+ content."
Selling Partner Insights (covers account_health.fetch, orders.summary, parts of analytics.fetch, connect.status, messaging.request_review). Per Amazon: "View information about the Amazon Selling Partner account and performance."
Brand Analytics (covers Brand Analytics report types in analytics.fetch; requires the buyer's Brand Registry enrollment in addition to the role). Per Amazon: "Access your sales and inventory data to manage your Amazon Retail business."

NOT requested (intentionally):

Inventory and Order Tracking role. AI Tools that need to read FBA inbound shipments, FBA inventory levels by warehouse, FBM order shipping details, or similar inventory/order-tracking data cannot be built on the SP-API integration today. Per Amazon: "Analyze and manage inventory. Does not include information required to generate shipping labels."
Finance and Accounting role. Although Amazon approved this role on SellerShorts' application, the broker does not request it at OAuth time today because none of the current AI Tools require financial-events data. The finance.summary capability is therefore not exposed to creators today. This reduces the platform's Data Protection obligation surface (financial events include order identifiers that are PII-adjacent). If a future tool concept needs financial data, SellerShorts will roll out scope-string + opt-in support deliberately. Per Amazon: "Produce account and financial statements. Does not include information required to generate tax invoices."
PII delegation via Restricted Data Token (RDT). SellerShorts declared "No" on the Amazon application: we do not delegate access to Personally Identifiable Information (PII) to creators. This means your AI Tool will never receive buyer names, shipping addresses, phone numbers, emails, or any other PII from the broker. Read capabilities like orders.summary return aggregated metrics only.

If your AI Tool concept requires Inventory tracking, financial-event-level data, raw order PII, or non-Seller (Vendor / Amazon Business) accounts, the SP-API integration is not the right fit today. Reach out to support if your use case is borderline.

📚 Amazon references: SP-API Roles overview · Role-to-operation mappings · SP-API Policies and Agreements (DPP + AUP)

Important: Amazon Policy Responsibility

📜 Your AI Tool must produce Amazon-policy-compliant content and actions

The SellerShorts broker forwards your AI Tool's requests to Amazon's API. Amazon's content, advertising, and communication policies apply to every request. The buyer (account holder) is ultimately responsible to Amazon for what is posted on their account, but as the AI Tool creator you are responsible for generating output that helps the buyer stay compliant.

Per-capability policy notes are shown in the capability sections below. Common rules that apply across capabilities:

Brand Registry is required for A+ Content (capability #12) and for Brand Analytics report types in analytics.fetch (capability #7).
Listing content rules (no promotional language, no competitor mentions, no HTML, character limits) apply to listings.update (#9).
Amazon image standards (white background, no watermarks, resolution minimums) apply to listings.update_images (#10).
Solicitations rate-limits (one per order, 5-30 days after delivery) are enforced by Amazon for messaging.request_review (#13).
Apply button preview must be truthful: the confirm.summary and confirm.diff_preview fields shown to the buyer must accurately describe what the broker will do. Misleading previews are grounds for tool de-listing.
No PII exposure: read capabilities (orders.summary, etc.) return aggregated metrics only. Your tool must not attempt to derive or infer buyer PII from the aggregate.

Amazon retains the right to take action against any seller whose listings, images, content, or messages violate policy, regardless of whether the violation came from a manual edit or an AI Tool. Build defensively.

📚 Amazon authoritative source: SP-API Policies and Agreements (Data Protection Policy, Acceptable Use Policy, Solution Provider Agreement).

Setting up Amazon Seller Central in your AI Tool

Step 1: Select Amazon Seller Central provider

In the Inputs step of the AI Tool submission wizard, expand the "Authentication & Access Requirements" section.

You'll see a card for "Amazon Seller Central" with the description that summarizes the broker's SP-API access (products, listings, catalog search, order aggregates, analytics, Solicitations, and Account Health). Inventory and Order Tracking, financial events, and PII are intentionally out of scope (see the approval-scope box above).

Click the Amazon Seller Central card to select it. When selected, the card shows a green checkmark and an "Enabled" status badge.

Step 2: Understand capabilities

Capabilities are permissions that define what your AI Agent can do with a buyer's Amazon Seller Central account.

When you select Amazon Seller Central, 11 capabilities are automatically enabled for your AI Agent (no configuration needed). An additional 3 Listings Items API capabilities are available on demand: listings.get (GET, reads a single listing's full attribute set), listings.update (PATCH write), and listings.update_images (PATCH write). You opt into them per-tool in the wizard's "Post to Amazon (Optional)" section, and admin reviews each tool's declared write actions before approval. Together these cover product listings (read + PATCH writes), catalog search, feed submission, order summary aggregates, analytics (Brand Analytics SQP + Sales/Traffic Reports), A+ content generation, Amazon's Request-a-Review flow, and Seller Performance / Account Health reports.

Available Capabilities (14 Total: 11 auto-enabled + 3 wizard-opt-in)

1. connect.status

Verify the buyer's Amazon Seller Central connection is active and check marketplace participations.

Use case: Confirm connection health before running expensive operations
SP-API endpoint: /sellers/v1/marketplaceParticipations

2. products.list

Fetch a list of products from the buyer's catalog.

Use case: Inventory audits, listing health checks, bulk operations
SP-API endpoint: Catalog Items API (v2022-04-01)

3. products.detail

Get detailed information about a specific product (ASIN, attributes, images, etc.).

Use case: Deep listing analysis, competitor research, optimization recommendations
SP-API endpoint: Catalog Items API (v2022-04-01)

4. catalog.search

Search the Amazon catalog by keywords to find competing or similar products.

Use case: Keyword research, competitive ASIN discovery, niche analysis
SP-API endpoint: GET /catalog/2022-04-01/items. See the Catalog Items API v2022-04-01 reference.

5. feeds.status

Check the status of submitted feeds (listings, inventory, pricing).

Use case: Monitor feed processing, verify bulk updates succeeded
SP-API endpoint: Feeds API v2021-06-30 reference

6. orders.summary

Aggregated order metrics (total orders, units, revenue). No buyer PII included.

Use case: Sales reporting, trend analysis, performance dashboards
Note: Uses aggregated metrics only. Does not access buyer names, emails, or shipping addresses

7. analytics.fetch

Fetch aggregated analytics data using async Reports API workflow (create request, then poll status, then download report).

Use case: Performance analyzers, sales trend reports, traffic analysis, keyword/search-query research
Report types: insights_summary (default), sales_traffic (Sales & Traffic Reports), brand_analytics_search_terms, brand_analytics_market_basket, brand_analytics_item_comparison, brand_analytics_search_query_performance (Brand Analytics SQP, added Phase 5)
Note: Brand Analytics reports require the seller's Amazon Brand Registry enrollment and the Brand Analytics role on their SP-API connection (see SP-API Roles).

8. listings.get Wizard opt-in

Retrieve a single product listing (attributes, images, descriptions, A+ Content references) by SKU.

Use case: Read current listing state before generating an updated version (Tool 1, Listing Fixer flow)
SP-API endpoint: Listings Items API (2021-08-01): GET /listings/2021-08-01/items/{sellerId}/{sku}
Opt-in required: Declare this verb in the wizard's "Post to Amazon (Optional)" section to use it. Not auto-enabled.

9. listings.update Wizard opt-in Apply button

Push listing patches (titles, bullets, descriptions, attribute changes) to a buyer's listing via PATCH.

Use case: AI-generated listing rewrites pushed to Amazon (Tool 1, Listing Fixer write path)
SP-API endpoint: Listings Items API (2021-08-01): PATCH /listings/2021-08-01/items/{sellerId}/{sku}
Opt-in required: Declare this verb in the wizard's "Post to Amazon (Optional)" section to use it. Not auto-enabled.
Apply button eligible: Buyers see a one-click "Apply to Amazon" button on the order page if you declare it in the wizard and leave the Show "Apply to Amazon" button after tool runs toggle ON (defaults to ON when you check a write verb).

⚠️ Amazon listing content policy (your AI Tool must respect):

Title length varies by category, generally ≤ 200 characters. Some categories enforce ≤ 80 characters.
No ALL CAPS (except for legitimate abbreviations like USB, LED).
No emojis, decorative special characters, or non-language symbols.
No HTML in bullets or descriptions (Amazon strips and may reject).
No competitor brand names. No "free shipping", "discount", or pricing in titles.
No medical/health claims unless substantiated and category-permitted.
No keyword stuffing (Amazon's algorithm and review team detect this).
Each attribute change is validated by Amazon at submission. Invalid changes are returned in the issues array of the response with severity ERROR or WARNING.

Your AI Tool generates the content; the buyer's account bears the policy responsibility. Repeated violations can lead to listing suppression or account-level actions against the buyer.

📚 Amazon references: Listings Items API v2021-08-01 reference

10. listings.update_images Wizard opt-in Apply button

Push image patches (main image, variant images, additional images) to a buyer's listing.

Use case: AI-generated product images pushed to Amazon (Tool 4, Product Image Maker write path). Images must be hosted on a publicly-accessible HTTPS URL.
SP-API endpoint: Listings Items API (2021-08-01) image-attribute PATCH
Opt-in required: Declare this verb in the wizard's "Post to Amazon (Optional)" section to use it. Not auto-enabled.
Apply button eligible: Write verb, eligible for Apply to Amazon when declared.

⚠️ Amazon image policy (your AI Tool must respect):

Main image rules: pure white background (RGB 255,255,255), product fills 85% of frame, no props, no watermarks, no overlay text, no badges, no borders.
Resolution: minimum 500px on longest side; 1600px or larger recommended for zoom functionality.
Format: JPEG (.jpg) is required for main images. Other slots accept JPEG, PNG, GIF (non-animated), TIFF.
Content rules: must show the actual product being sold. No nudity, no offensive content, no copyrighted material you don't own rights to, no competitor branding.
Additional image slots (PT01-PT08, SWCH for variant swatches) have looser rules but still no offensive content and no false claims.
URL must be publicly fetchable HTTPS. Amazon's image-fetcher does not authenticate. Pre-signed S3 URLs that expire too quickly will fail.

Amazon's image-fetch step runs server-side; non-compliant images may be silently ignored or trigger account-level warnings to the buyer.

📚 Amazon references: Product image guide (Seller Central) · Listings Items API reference

11. listings.upload_feed

Submit listing updates or creations to Amazon via Feeds API (bulk path).

Use case: Bulk listing updates, inventory sync, pricing adjustments. For single-listing edits, prefer listings.update (PATCH) which is faster and simpler.
Feed types: The feed_type parameter is a free string (any Amazon-supported feed type can be passed). For Listings, Amazon has deprecated the legacy XML/flat-file types; only JSON_LISTINGS_FEED is active for new Listings submissions (verified 2026-05-28 against developer-docs.amazon.com/sp-api/docs/feed-type-values). Other feed categories (FBA, Orders, Easy Ship, Invoicing) still accept their existing feed type values.
Content types: The broker accepts text/xml (default, backward compat for non-Listings categories), text/tab-separated-values, text/plain, and application/json (required for JSON_LISTINGS_FEED, added Phase 6 Item 9).
Note: Amazon removed the POST_INVENTORY_AVAILABILITY_DATA XML inventory feed on July 31, 2025. Use Listings Items PATCH (listings.update) for inventory mutations instead.

12. listings.a_plus_generate Apply button

Create or update A+ Content modules (Enhanced Brand Content).

Use case: AI-generated A+ content modules, premium listing pages (Tool 5, A+ Content Maker write path)
SP-API endpoint: A+ Content API: POST /aplus/2020-11-01/contentDocuments
Apply button eligible: Write verb, eligible for Apply to Amazon when declared in the wizard.

⚠️ Amazon A+ Content policy constraints:

Brand Registry required. A+ Content is only available to sellers enrolled in Amazon Brand Registry.
No competitor mentions or comparisons.
No medical claims, no FDA-regulated category claims unless properly substantiated.
No promotional language ("best", "#1", "guaranteed", "satisfaction guaranteed"), no pricing or shipping claims.
Images embedded in A+ must follow Amazon's image standards (no watermarks, no overlay text beyond what Amazon allows for specific modules, no third-party logos).
Amazon reviews all submitted A+ Content before publishing. Non-compliant submissions are rejected (creator's tool must handle rejection gracefully).

Your AI Tool is responsible for generating content that respects these rules. Amazon's review step is the final gate; non-compliant content will not go live.

📚 Amazon references: A+ Content API use case guide · Amazon Brand Registry eligibility

13. messaging.request_review Apply button

Trigger Amazon's official "Request a Review" email flow on a buyer order (Solicitations API). This is the Amazon-sanctioned mechanism for asking buyers to leave a review.

Use case: Tool 7 (Review Reply Writer) "Request a Review" button. Sends a standard Amazon-template review request for a specific completed order.
SP-API endpoint: Solicitations API v1: POST /solicitations/v1/orders/{amazonOrderId}/solicitations/productReviewAndSellerFeedback
Note: The amazonOrderId path parameter is Amazon's order ID (e.g., 123-1234567-1234567), not SellerShorts' internal order ID.
Apply button eligible: Write verb, eligible for Apply to Amazon when declared in the wizard.

⚠️ Amazon policy constraints (sellers/buyers responsible for following):

Amazon allows at most one solicitation per order. Subsequent attempts on the same order are rejected by Amazon.
The solicitation can only be sent between 5 and 30 days after delivery per Amazon's Communication Guidelines.
You cannot add custom messaging. Amazon sends its standard template only.
Incentivizing reviews is prohibited under Amazon's Anti-Manipulation Policy. Your tool should not condition Request-a-Review on offers, discounts, or buyer behavior.
Some product categories (e.g., adult, regulated goods) may restrict review solicitations entirely.

If Amazon rejects the solicitation for any of these reasons, the broker returns the error response from Amazon. The buyer (account holder) is ultimately responsible for compliance.

📚 Amazon references: Solicitations API use case guide · Solicitations v1 reference

14. account_health.fetch

Fetch the seller's Account Health / Seller Performance report via async Reports API workflow.

Use case: Tool 9 (Suspension Appeal Writer) auto-pull, fetches the seller's current Account Health report instead of requiring the buyer to manually paste the Amazon notification.
SP-API endpoint: Reports API v2021-06-30: reportType: GET_V2_SELLER_PERFORMANCE_REPORT (async workflow: create request, then poll status, then download report). Roles required by Amazon: Selling Partner Insights. Availability: Sellers only. Requested-only (cannot be scheduled).

(Capabilities 8-10 are the Listings Items API verbs (one GET read and two PATCH writes) added in the 2026-05-27 listings PATCH pass. Capabilities 13-14 (Solicitations and Account Health Reports) were added in the 2026-05-28 Phase 1-6 capability gap closure. They all reuse the existing Amazon Seller Central OAuth connection, so no new connection type was introduced. The broker requests three SP-API roles at OAuth time: Product Listing, Selling Partner Insights, and Brand Analytics. If a future verb requires a different role, the seller would need to re-authorize.)

Calling the Capabilities API

All Amazon Seller Central SP-API calls go through SellerShorts' capabilities API endpoint:

Base URL: https://sellershorts.com/api/capabilities

To make SP-API calls, send requests to the capabilities API endpoint with the job_token in the Authorization header:

POST https://sellershorts.com/api/capabilities
Authorization: Bearer {job_token}
Content-Type: application/json

{
  "capability": "products.list",
  "provider": "amazon",
  "params": {
    "marketplace_id": "ATVPDKIKX0DER",
    "page_size": 20
  }
}

Example: Check Connection Status

POST https://sellershorts.com/api/capabilities
Authorization: Bearer {job_token}
Content-Type: application/json

{
  "capability": "connect.status",
  "provider": "amazon",
  "params": {}
}

Example: Search the Catalog

POST https://sellershorts.com/api/capabilities
Authorization: Bearer {job_token}
Content-Type: application/json

{
  "capability": "catalog.search",
  "provider": "amazon",
  "params": {
    "keywords": "wireless headphones",
    "marketplace_id": "ATVPDKIKX0DER",
    "page_size": 20
  }
}

Example: Fetch Order Summary

POST https://sellershorts.com/api/capabilities
Authorization: Bearer {job_token}
Content-Type: application/json

{
  "capability": "orders.summary",
  "provider": "amazon",
  "params": {
    "marketplace_id": "ATVPDKIKX0DER",
    "start_date": "2026-01-01T00:00:00Z",
    "end_date": "2026-01-31T23:59:59Z",
    "granularity": "DAY"
  }
}

Multi-Marketplace Support

When a buyer authorizes Amazon Seller Central, SellerShorts saves one connection per marketplace their account participates in. For example, a North American seller may have 3 connections (US, Canada, Mexico) under a single authorization.

To target a specific marketplace in your API calls, pass marketplace_id in the params. SellerShorts will route the request to the correct regional endpoint automatically (NA, EU, or FE).

Supported Marketplace IDs

Region	Country	Marketplace ID
NA	🇺🇸 United States	`ATVPDKIKX0DER`
NA	🇨🇦 Canada	`A2EUQ1WTGCTBG2`
NA	🇲🇽 Mexico	`A1AM78C64UM0Y8`
NA	🇧🇷 Brazil	`A2Q3Y263D00KWC`
EU	🇬🇧 United Kingdom	`A1F83G8C2ARO7P`
EU	🇩🇪 Germany	`A1PA6795UKMFR9`
EU	🇫🇷 France	`A13V1IB3VIYZZH`
EU	🇮🇹 Italy	`APJ6JRA9NG5V4`
EU	🇪🇸 Spain	`A1RKKUPIHCS9HS`
EU	🇳🇱 Netherlands	`A1805IZSGTT6HS`
EU	🇧🇪 Belgium	`AMEN7PMS3EDWL`
EU	🇸🇪 Sweden	`A2NODRKZP88ZB9`
EU	🇵🇱 Poland	`A1C3SOZRARQ6R3`
EU	🇮🇪 Ireland	`A28R8C7NBKEWEA`
EU	🇪🇬 Egypt	`ARBP9OOSHTCHU`
EU	🇦🇪 UAE	`A2VIGQ35RCS4UG`
EU	🇸🇦 Saudi Arabia	`A17E79C6D8DWNP`
EU	🇹🇷 Turkey	`A33AVAJ2PDY3EV`
EU	🇿🇦 South Africa	`AE08WJ6YKNBMC`
EU	🇮🇳 India	`A21TJRUUN4KGV`
FE	🇯🇵 Japan	`A1VC38T7YXB528`
FE	🇸🇬 Singapore	`A19VAU5U5O7RUS`
FE	🇦🇺 Australia	`A39IBJ37TRP1C6`

Error Handling

All possible error codes returned by the capabilities API for Amazon Seller Central:

INVALID_TOKEN: job_token missing or invalid
CAPABILITY_NOT_ALLOWED: capability not enabled for this AI Tool
TOKEN_EXPIRED: buyer's Amazon connection has been revoked, ask them to reconnect
NO_CONNECTION: buyer has not connected Amazon Seller Central yet
SP_API_ERROR: Amazon's SP-API returned an error
RATE_LIMIT: too many requests, retry with backoff
INVALID_REQUEST: request body is invalid
ORDER_NOT_FOUND: order ID in token does not exist
INTERNAL_ERROR: unexpected server error

Best Practices

Use capabilities appropriately

11 standard capabilities are automatically enabled when you select Amazon Seller Central, plus 3 additional Listings Items API verbs (one GET read and two PATCH writes) available on opt-in via the wizard. While you have access to all capabilities your tool declares, design your AI Agent to only use the capabilities it actually needs. This follows the principle of least privilege and makes your AI Tool's behavior clearer to buyers.

Test thoroughly

Connect your own Amazon Seller Central account during development. Verify that:

OAuth connection completes successfully
All required capabilities are working
Error handling is robust
Results are accurate and complete

Document for buyers

Be explicit in your AI Tool description about:

Why the Amazon Seller Central connection is needed
That seller must be the PRIMARY user of their Seller Central account
Which capabilities your AI Agent uses and why
What data the tool produces

Frequently Asked Questions

Do I need my own Amazon Seller Central account to publish an AI Tool?

No. You don't need an Amazon Seller Central account to publish an AI Tool. Buyers connect their own accounts when they run your AI Tool.

Can I test my AI Tool without a buyer account?

Yes. You can connect your own Amazon Seller Central account to test the integration end-to-end before publishing.

What happens if a buyer doesn't have an Amazon Seller Central account?

They cannot run your AI Tool. The connection step is required, and they'll see instructions to authorize Amazon Seller Central if they haven't yet.

Which Amazon marketplaces are supported?

All 23 official Amazon marketplaces are supported across North America (US, Canada, Mexico, Brazil), Europe (UK, Germany, France, Italy, Spain, Netherlands, Belgium, Sweden, Poland, Ireland, Egypt, UAE, Saudi Arabia, Turkey, South Africa, India), and Far East (Japan, Singapore, Australia). Sellers connect once and access is granted to every marketplace their account participates in.

What capabilities are available for Amazon Seller Central?

When you select Amazon Seller Central, 11 SP-API capabilities are automatically enabled: connect.status, products.list, products.detail, catalog.search, feeds.status, orders.summary, analytics.fetch (Brand Analytics SQP + Sales/Traffic Reports), listings.upload_feed, listings.a_plus_generate, messaging.request_review (Solicitations API), and account_health.fetch (Seller Performance Reports). An additional 3 Listings Items API capabilities (listings.get, listings.update, listings.update_images) are available on opt-in via the wizard's "Post to Amazon (Optional)" section. Note: financial data (Finances API) is intentionally out of scope today; no current tool requires it.

Can I change capabilities after my AI Tool is approved?

Currently, edits to an approved AI Tool are not automatically re-reviewed. If you change capabilities, submit your AI Tool for admin re-review to stay aligned with platform policy.

Who must approve the seller authorization?

Per Amazon's policy, the seller must be logged into Amazon Seller Central as the PRIMARY user (account owner) before authorizing your AI Tool. Secondary users (even admins) cannot complete the authorization.

Do buyers need to reconnect their Amazon Seller Central account for each order?

No. Once a buyer connects, the connection persists across orders. They only need to reconnect if they manually disconnect or if their tokens are revoked by Amazon.

Need help? See the Inputs guide, the Callback guide, or contact support.