Seller intelligence

Seller intelligence with marketplace context intact

Connect public seller facts to the offers and product records that reference them without turning a marketplace handle into an inferred legal identity.

Start free See the recipe

/api/amazon

One seller, the public evidence around it

GET/api/amazon/sellerGET/api/amazon/product/offersGET/api/amazon/productGET/api/amazon/product/sales

Amazon seller identifiers are marketplace-scoped public identifiers. Glade API preserves that boundary while providing the offer, product, availability, and modeled context teams need for responsible seller research.

What teams build with it

Each pattern begins with observable marketplace facts and keeps inference outside the acquisition layer.

Seller profile with offer evidence

Resolve the marketplace seller record, then inspect the offers that name it in product context.

Endpoint chainseller -> offers -> product

Catalog participation

Start with product search and map which sellers appear across the resulting offer sets.

Endpoint chainsearch -> product -> offers

Buy-box visibility

Keep seller, condition, delivery, price, and buy-box signals together for the observation.

Endpoint chainoffers -> seller

Availability context

Attach an explicit stock estimate instead of inferring inventory from seller presence alone.

Endpoint chainoffers -> stock

Modeled sales context

Use versioned product-level estimates as context without claiming seller-reported sales.

Endpoint chainproduct -> sales

Deal participation

Find active deals, resolve the products, and inspect the public seller and offer facts behind them.

Endpoint chaindeals -> product -> offers

How the seller intelligence workflow works

Four operations connect a marketplace-scoped seller identifier to current public commercial context.

The response represents public marketplace facts. It does not verify legal identity, beneficial ownership, or off-platform relationships.

GET /api/amazon/seller
Resolve the marketplace seller record
Pass a documented seller identifier and domain so the identifier is never interpreted outside its market.
marketplace-scoped identity
GET /api/amazon/product/offers
Inspect the offers that reference it
Capture condition, price, delivery, availability, Prime, and buy-box context for each observation.
volatile cache · 5 minutes
GET /api/amazon/product
Attach the stable product record
Keep offer observations joined to a durable ASIN, title, identifiers, images, and marketplace context.
catalog cache · 6 hours
GET /api/amazon/product/sales
Add labeled demand context
Use an immutable model version and never present an estimate as seller-reported sales.
estimated, not declared

APIs used in seller intelligence

Open each bounded operation to inspect its inputs, freshness policy, and the public facts it returns.

Compared with the usual setup

Seller research is safer when observable marketplace facts stay separate from identity and ownership inference.

Capability	Glade API	Typical setup
Seller identity	Identifiers remain scoped to their selected Amazon marketplace.	A handle is sometimes treated as a verified legal entity without supporting evidence.
Offer context	Condition, price, delivery, availability, Prime, and buy-box signals stay together.	A seller and price are extracted without the delivery or condition context that changes their meaning.
Sales language	Derived estimates are labeled and carry immutable model versions.	Modeled or inferred values can be displayed as if the seller reported them.
Freshness	Fetched time, cache state, and operation-specific TTLs travel with the result.	Freshness is inferred from a job timestamp or omitted entirely.
Failure handling	Typed failures stay separate from empty or out-of-stock results.	Retries, proxy failures, parser failures, and empty pages can look alike.
Pricing model	Successful normalized operations consume one published request unit.	Proxy, browser, compute, storage, and maintenance costs are metered separately.

Seller intelligence questions

Is a seller ID globally unique?+

Treat it as marketplace scoped. Always retain the selected Amazon domain with the identifier and returned record.

Does Glade verify a seller's legal identity?+

No. Glade represents observable public marketplace facts and does not infer or verify legal identity.

Can I see which offers reference a seller?+

Use offer records in product context and retain the seller, condition, price, delivery, and observation metadata together.

Are sales figures seller-reported?+

No. Sales estimates are derived, explicitly labeled, and associated with an immutable model version.

Can I export seller research?+

Normalized records can feed organization-scoped export workflows while preserving the marketplace and request metadata used to produce them.

How current are offer observations?+

Offers use a five-minute cache policy because price, seller, delivery, and availability are volatile.

Ask AI about Glade API

Ask ChatGPT Ask Perplexity Ask Gemini Ask Claude Ask Grok

Inspect a seller with context attached

Start from a marketplace-scoped identifier, then connect it to current offer and product evidence.

Start free Read the docs

Request

curl -G "https://gladeapi.com/api/amazon/seller" \
  -H "API-KEY: glade_live_YOUR_API_KEY" \
  --data-urlencode "sellerId=ATVPDKIKX0DER" \
  --data-urlencode "domain=US"

curl -G "https://gladeapi.com/api/amazon/product/offers" \
  -H "API-KEY: glade_live_YOUR_API_KEY" \
  --data-urlencode "asin=B0D1XD1ZV3" \
  --data-urlencode "domain=US"

Both calls use the same key, response envelope, request metadata, and documented failure model.