Different sources. Different formats.
Product details, prices and availability vary across marketplaces.
Access structured ecommerce data through SellerApp APIs. Build analytics, research tools and custom dashboards.
Product listing

Built and run by your team
Start with marketplace data.
Receive a structured API response.
Build your experience with the data.
Product details, prices and availability vary across marketplaces.
Your team must collect, standardize, check and maintain the data before using it.
Use SellerApp APIs as your data starting point, then build your application.
Your team owns storage, business rules and application logic.
Give your engineers more room to build your product.
Four data types. Clear origins. Practical uses.
Access product attributes, pricing, ratings and other marketplace information.
Read the listing
Structure the fields
Power product research
Published API coverage
Availability: confirm with API team
/products/reviews/bestsellers·/categories/keyword-search·/keyword-metrics·/keyword-research/vendor/*·/ads/*Sales estimates come from Product Details. Availability signals: confirm scope.
Published API coverage
Availability, derived, account: confirm with API team
/walmart/products/walmart/keyword-searchAttributes, pricing, seller and rating signals. Review text, availability and estimates: confirm scope.
Published API coverage
Availability, derived, account: confirm with API team
/lazada/products/lazada/keyword-searchPrice, seller, rating and competitor attributes. Other datasets: confirm scope.
Published API coverage
Availability, derived, account: confirm with API team
/shopee/products/shopee/keyword-searchPrice, seller, fulfilment method and rating signals. Other datasets: confirm scope.
Published API coverage
Not yet in the published API reference.
All datasets: confirm with API team
Listed among SellerApp’s marketplaces. Endpoints and fields are confirmed with the API team.
| Marketplace | Product | Pricing | Ratings · reviews | Search | Availability | Derived | Account |
|---|---|---|---|---|---|---|---|
Amazon | Documented | Documented | Documented | Documented | To confirm | Documented | Documented |
| Walmart | Documented | Documented | Documented | Documented | To confirm | To confirm | To confirm |
| Lazada | Documented | Documented | Documented | Documented | To confirm | To confirm | To confirm |
| Shopee | Documented | Documented | Documented | Documented | To confirm | To confirm | To confirm |
| Best Buy | To confirm | To confirm | To confirm | To confirm | To confirm | To confirm | To confirm |
Product details from Amazon
Insulated Water Bottle, 750 mlAmazon product IDB0EXAMPLE01Choose a product
{
"title": "Insulated Water Bottle, 750 ml",
"listing_price_new": 39.00,
"currency_code": "USD",
"ratings": 4.8
}Receive product fields

Build a research view
SellerApp provides the data. Your team builds the experience.
Requests send client-id and token headers with SellerApp-issued credentials. Keep them server-side.
--header 'client-id: YOUR_CLIENT_ID' --header 'token: YOUR_TOKEN'
https://api.sellerapp.com/sellmetricsv2 + endpointgeo sets the Amazon marketplaceproductIds or keyword/walmart/productsJSON. Product Details groups fields into product_attributes, price_details, fee_details, product_potential and ratings. Other endpoints have their own schema.
Some APIs use an asynchronous pattern: submit a bulk request, get a report id, then fetch the report, e.g. /keyword-research/bulk and /keyword-research/bulk/report.
Request examples are in the Postman references. We don’t list SDKs because none are published.
Build customer-facing software features.
Connect ecommerce data to pipelines and warehouses.
Build dashboards and custom reporting.
Create models from observed and derived datasets.
Build research and intelligence capabilities.
Use the resulting analytics to decide.
Source: SellerApp API Solutions and API Case Study documents. Each customer used a different API category. No figures are claimed.
Product data (attributes, pricing, fees, ratings, reviews, rank, categories), keyword and search data, sales estimates, listing-quality scores, and authorized Vendor Central and advertising reports. Coverage varies by marketplace.
The published reference documents Amazon, Walmart, Lazada and Shopee endpoints. SellerApp lists further marketplaces; confirm the ones you need.
The call pattern is consistent. Fields differ by marketplace, so map them per source.
Confirm with the API team. Historical availability differs by dataset.
Confirm with the API team per dataset and marketplace.
Observed data is collected from marketplaces, such as a listing price. Estimated data is modelled, such as sales estimates, and should be shown as an estimate.
Yes, where the account owner authorizes it, for example Vendor Central and advertising reports. There’s no access to private account data without authorization.
Confirm the authorization flow with the API team for each account dataset.
Yes. Your application joins records by identifiers such as ASIN, normalizes fields and applies your rules.
JSON over authenticated REST requests.
Yes, limits depend on your plan and are confirmed during evaluation.
Some APIs, such as Keyword Research Bulk, use a submit-then-fetch report pattern. Confirm for other datasets.
That’s set in your agreement. Confirm your use case with the API team.
Storage, caching and redistribution terms are set in your agreement.
By use case, marketplaces, datasets, volume, refresh frequency, history and support. Build a requirements brief.
Ask the API team about evaluation access.
Technical guidance within an agreed support scope. Talk to us about what your team needs.
Confirm with the API team how changes are communicated and handled.
Log response status, retry transient failures with backoff, store timestamps and show users when data was last observed.
Marketplace APIs mainly cover your own authorized account. SellerApp adds structured product, competitor, keyword and estimate data across marketplaces.
Sales estimates, authorized sales history and Vendor Central forecasting reports are typical inputs. Your model runs in your application.
Both. Observed data, plus derived metrics such as sales estimates, relevancy scores and listing-quality scores.
Tell us what you’re building, which marketplaces matter, and the data your application needs. We’ll help you evaluate SellerApp’s Ecommerce Data API for your use case.