Amazon Sales API

Build sales intelligence into your Amazon software.

Bring sales insights into the tools your customers already use. Explore the data and integration approach with SellerApp.

Discuss your integration

Explore the data

What you can build

What could your product help sellers decide?

Understand demand

Help users interpret sales patterns for a product, when the data they need is available for that marketplace.

Built on: product sales estimates, or authorized account sales.

Compare opportunities

Support side-by-side product comparisons, with each figure clearly marked as an estimate or as account data.

Built on: product sales estimates with price, fees and rank.

Plan the next move

Feed supported sales signals into the planning and reporting workflows your product already runs.

Planning logic is built in your application. It isn’t returned by the API.

The data

Know what you’re building with.

Discuss data requirements

1 · Product sales estimates

Estimated sales

EstimateEstimated range

Understand potential demand, not actual orders.

2 · Product context

Price

Fees

Rank & ratings

See the listing details behind the estimate.

3 · Authorized account sales

Seller accountAccount authorized

Account sales

Account owner authorization required.

Use sales data from an account you can access.

4 · Calculated insights

Sales data

Actual costs

Profitability

Sales$24,990

Your costs$15,460

Margin38%

Combine sales with your costs in your application.

How it fits

From a data request to a useful product feature.

Define the requirement

Identify the use case, the data it needs and any access conditions. For example, a product-comparison view built on sales estimates for one marketplace.

You and the API team

Connect the API

Your backend sends an authenticated request for the product and marketplace. SellerApp returns a JSON response.

SellerApp supplies

curl --location 'https://api.sellerapp.com/sellmetricsv2/products?product_specifications=1&price_detail=1&fee_detail=1&ratings=1&geo=us&productIds=B0SAMPLE01' \
  --header 'client-id: your-client-id' \
  --header 'token: your-token'

// trimmed
[{
  "product_attributes": { "asin": "B0SAMPLE01", … },
  "price_details": { "listing_price_new": 39.00, "currency_code": "USD" },
  "fee_details": { "referral_fee": 5.85, "fba_fee": 4.37 },
  "product_potential": {
    "sales_estimate_low": 3166,
    "revenue_estimate_high": 31500, …
  }
}]

Sample from the Product Details reference. Placeholder ASIN and credentials, not a live call.

Use the response

Map the returned fields into your report, application view or internal workflow. Add your own inputs where a feature needs them.

Your software builds

Insulated Water Bottle, 750 mlExample product

Use case Product comparison view

DataSales estimatePrice and fees

Marketplace Amazon.com

Access SellerApp API credentials

curl --location 'https://api.sellerapp.com/sellmetricsv2/products?product_specifications=1&price_detail=1&fee_detail=1&ratings=1&geo=us&productIds=B0SAMPLE01' \
  --header 'client-id: your-client-id' \
  --header 'token: your-token'

// trimmed
[{
  "product_attributes": { "asin": "B0SAMPLE01", … },
  "price_details": { "listing_price_new": 39.00, "currency_code": "USD" },
  "fee_details": { "referral_fee": 5.85, "fba_fee": 4.37 },
  "product_potential": {
    "sales_estimate_low": 3166,
    "revenue_estimate_high": 31500, …
  }
}]

Sample from the Product Details reference. Placeholder ASIN and credentials, not a live call.

Your application · Compare

Insulated Water Bottle, 750 mlExample product · Amazon.com

Estimated sales rangeproduct_potential

Price and Amazon feesprice_details · fee_details

Margin column+ your cost inputs

Decisions it can support

Turn sales data into useful decisions.

Power these experiences in your application.

Sales trends

Is demand changing?

Use sales estimates or authorized sales history.

Illustrative dataDemand trending up

Profitability

What’s left after costs?

Combine account sales, fees and your actual costs.

Illustrative data34.4% margin

Inventory planning

When should you restock?

Combine sales velocity with current inventory.

Illustrative dataReorder point approaching

Forecasting

What could demand look like?

Use historical sales in your forecasting model.

Illustrative dataEstimate, not a guarantee

For technical evaluators

Evaluate the integration before you commit.

Documented

Response format and documentation

Responses are JSON. The endpoint reference is published in Postman.

Open the reference

Documented

Authentication and authorization

Requests carry client-id and token headers. Account-level data also needs authorization from the account owner.

Confirm with API team

Coverage and data freshness

Marketplaces, categories and refresh frequency for each data type.

Confirm with API team

Historical availability

How far back each data type goes, and whether history is available from day one.

Confirm with API team

Request limits and expected volume

Limits depend on the plan. Share your expected volume so we can size it.

Support offered

Error handling and integration support

Our team supports you during integration. Error handling is covered when we review your requirements.

Review requirements with the API team

Case study summary

A practical application: better sales planning.

Based on sales estimates

Challenge

Uncertain demand

Forecasts, benchmarks and stock decisions lacked reliable sales context.

Approach

Sales estimates via the API

Estimates fed market-trend, seasonality and competitor analysis.

Reported outcome

Better-informed planning

More confident forecasts and inventory decisions.

5MAPI requests / day

2,200API users

99%Published uptime

Getting started

Start with your use case.

Share what you’re buildingYour product, its users and the decisions sales data should support.
Confirm data fit, access and commercialsData types, marketplaces, authorization, expected volume and pricing for your plan.
Integrate with documentation and supportBuild against the published reference, with our team on hand for questions.

Talk to the API team

FAQ

Questions developers ask before building

Does this API provide sales estimates or actual seller-account data?add

They’re separate. Product sales estimates are modelled ranges available for products in supported marketplaces. Actual sales data comes only from an account that has authorized access. Vendor Central reporting is documented today. Ask us about Seller Central coverage for your use case.

What authorization is required?add

Every request uses your SellerApp API credentials, sent as client-id and token headers. Account-level sales data also requires authorization from the account owner. We walk you through that process during onboarding.

Which marketplaces and product categories are supported?add

Coverage differs by data type. Tell us which marketplaces and categories you need, and we’ll confirm what’s available for each before you integrate.

How current is the data?add

Refresh frequency varies by data type. We confirm it for the data your product depends on during the requirements review.

What historical data is available?add

Historical sales data is available. How far back it goes depends on the data type and marketplace, and we confirm it for your requirements.

How do request limits and pricing work?add

Plans are set around the data you need and how often you call it, so request limits vary by plan. Share your expected volume and we’ll propose a plan.

Can I review a sample response and documentation?add

Yes. The endpoint reference is published, including a sample Product Details response with sales-estimate fields.

What support is available during integration?add

Along with the documentation, our API team helps you integrate and answers questions as you build.

Talk to the API team

Tell us what you’re building.

Let’s confirm the data and integration approach that fit your product.

Which data types fit your use case
Marketplace coverage, freshness and history
Access requirements, volume and pricing