Amazon APIsellercentral.amazon.com ↗
Search and retrieve Amazon Seller Central Forum threads and replies. Access discussion metadata, post content, votes, and author data via 2 endpoints.
What is the Amazon API?
This API provides access to Amazon Seller Central Forums through 2 endpoints, returning discussion summaries and full thread content including replies. The search_discussions endpoint supports free-text search, date range filtering, sort order, and cursor-based pagination. The get_thread endpoint returns the original post body, reply objects with vote counts, view count, author usernames, and Amazon staff reply indicators for any thread UUID.
curl -X GET 'https://api.parse.bot/scraper/ca9f6f54-50a9-4798-adb2-78e734e1fa25/search_discussions?sort_by=relevance&date_range=pastDay&search_term=FBA+shipping&replies_filter=hasReplies' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace sellercentral-amazon-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Amazon Seller Central Forums SDK — search discussions, drill into threads."""
from parse_apis.sellercentral_amazon_com_api import (
SellerForums,
SortBy,
DateRange,
RepliesFilter,
ThreadNotFound,
)
client = SellerForums()
# Search recent discussions about FBA, sorted by latest activity
for summary in client.thread_summaries.search(
search_term="FBA shipping",
sort_by=SortBy.LAST_ACTIVITY_TIME,
date_range=DateRange.PAST_WEEK,
replies_filter=RepliesFilter.HAS_REPLIES,
limit=5,
):
print(summary.title, f"| replies: {summary.total_replies}")
# Drill down: grab the first result and fetch its full thread details
summary = client.thread_summaries.search(
search_term="FBA shipping",
date_range=DateRange.PAST_MONTH,
limit=1,
).first()
if summary is not None:
thread = summary.details()
print(f"\n--- {thread.title} ---")
print(f"Author: {thread.author} | Views: {thread.view_count} | Replies: {thread.total_replies}")
for reply in thread.replies:
print(f" {reply.author}: {reply.content[:80]}")
# Point lookup by thread_id discovered from the search above
if summary is not None:
try:
detail = client.threads.get(thread_id=summary.thread_id)
print(f"Fetched thread: {detail.title}")
except ThreadNotFound:
print("Thread was removed or does not exist.")
print("\nexercised: thread_summaries.search / ThreadSummary.details / threads.get")
Search and browse Amazon Seller Central Forums discussions. Supports text search, sorting, date filtering, and cursor-based pagination. Returns discussion summaries with metadata. When no search_term is provided, returns all discussions matching the filters. Each page returns up to `limit` results along with a next_page_token for fetching subsequent pages.
| Param | Type | Description |
|---|---|---|
| limit | integer | Number of results per page (1-50). |
| sort_by | string | Sort order for results. |
| date_range | string | Time window filter for discussions. |
| page_token | string | Pagination cursor from a previous response's next_page_token. Pass unchanged to fetch the next page. |
| search_term | string | Free-text search query to filter discussions (e.g. 'FBA shipping'). Omitting returns all discussions matching other filters. |
| replies_filter | string | Filter by reply status. |
{
"type": "object",
"fields": {
"discussions": "array of discussion summary objects",
"total_count": "integer, total number of matching discussions (may be approximate)",
"next_page_token": "string or null, cursor for fetching the next page"
},
"sample": {
"data": {
"discussions": [
{
"tags": [
"amzn1.spce.tag.8b1b5578",
"amzn1.spce.tag.8b1b1798"
],
"title": "Need Assistance: FBA Shipping Complaint Misplaced as 1-Star Product Review (Case ID:21308850761)",
"author": "Seller_xGL3L8wvzP5to",
"post_id": "b11efec3-e02c-4aa6-b474-527e3afe3122",
"up_votes": 0,
"is_pinned": false,
"thread_id": "b11efec3-e02c-4aa6-b474-527e3afe3122",
"created_at": 1784880946572,
"down_votes": 0,
"category_id": "amzn1.spce.category.8b1ad8dc",
"total_views": 22,
"has_solution": false,
"total_replies": 6,
"content_preview": "Need Assistance: FBA Shipping Complaint...",
"has_amazon_reply": true,
"last_activity_time": 1786326481188
}
],
"total_count": 10000,
"next_page_token": "27.437807,334d10e6-af36-4bc4-bb53-b5b69643424f"
},
"status": "success"
}
}About the Amazon API
Endpoints
The search_discussions endpoint returns a paginated list of forum discussion summaries. You can pass a search_term to filter by keyword (e.g., 'FBA shipping'), a date_range to scope results to a time window, a sort_by value to control ordering, and a replies_filter to narrow by reply status. Each response includes a discussions array, a total_count (which may be approximate), and a next_page_token string you pass unchanged to fetch the next page. Pages return up to 50 results when limit is set to its maximum.
Thread Detail
The get_thread endpoint takes a thread_id UUID — obtained from search_discussions results — and returns the full thread. Response fields include title, author, content (HTML), created_at (Unix timestamp in milliseconds), up_votes, down_votes, view_count, and a tags array. The replies array covers top-level replies from the initial page, each carrying post_id, content, author, created_at, up_votes, down_votes, reply_count, is_amazon_replied, and reply_to_id.
Reply Depth and Pagination
The get_thread endpoint returns approximately 8 top-level replies per call, reflecting the first page of replies as loaded for a given thread. Nested replies (children of top-level replies) are indicated via reply_to_id and reply_count fields but are not recursively fetched by this endpoint. The is_amazon_replied field on each reply object flags whether an Amazon staff member contributed to that branch of the thread.
The Amazon API is a managed, monitored endpoint for sellercentral.amazon.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when sellercentral.amazon.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official sellercentral.amazon.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Monitor seller community discussions about FBA policy changes using
search_termanddate_rangefilters - Identify threads with no replies using
replies_filterto find unanswered seller questions - Track which forum threads have received Amazon staff responses via the
is_amazon_repliedfield - Aggregate vote data (
up_votes,down_votes) across threads to surface the most contested seller topics - Build a digest of high-
view_countthreads to surface trending seller concerns - Extract thread
tagsarrays to categorize discussions by topic area for content analysis - Feed seller troubleshooting content into internal knowledge bases using
contentfields fromget_thread
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Amazon Seller Central have an official developer API for forum data?+
What does `get_thread` return for replies, and are nested replies included?+
get_thread endpoint returns up to approximately 8 top-level replies from the first page of a thread. Each reply object includes content, author, created_at, up_votes, down_votes, reply_count, is_amazon_replied, and reply_to_id. Nested replies (children of top-level replies) are not recursively fetched; reply_count and reply_to_id indicate their presence but the content is not included in the response.Does the API support paginating through all replies in a long thread?+
get_thread endpoint returns only the first page of replies, roughly 8 top-level items. Cursor-based pagination is available in search_discussions via next_page_token, but reply pagination within a thread is not exposed. You can fork the API on Parse and revise it to add a replies-pagination endpoint.How current is the forum data returned by `search_discussions`?+
date_range filter lets you scope results to recent windows such as the past year, but there is no documented real-time freshness guarantee. The total_count field in search results may also be approximate rather than exact.Can I retrieve seller profile pages or reputation data for forum authors?+
author username string in both discussion summaries and reply objects, but no further profile data — badges, post history, or account standing — is exposed. You can fork the API on Parse and revise it to add a seller profile endpoint.