Get a key and make your first call in about five minutes. Everything after that is the same three ideas: resolve an identifier, read the offers, ask what they mean.
Three paths in, depending on what you are building.
What people build first, and the pages that get them there.
Time-weighted percentile against a product’s own history at that seller.
AlertsStanding conditions with signed callbacks, scoped to a product, brand or category.
SearchKeyword when they know the model, semantic when they know the problem.
AnalysisNDJSON or Parquet. Analysts should not paginate an API to build a model.
The four that decide whether an integration survives real traffic. Most outages in this category trace back to one of them.
Every error shape the API returns, what causes it, and which ones are safe to retry.
Required readingPer-key limits, the headers that report them, and how to back off correctly.
Required readingSignature verification, replay protection and the mistakes that make webhook endpoints exploitable.
Required readingDate-based API versions, what counts as a breaking change, and how upgrades work.
Getting started — Quickstart · Authentication · SDKs and clients · Testing
Core concepts — Identifiers · The provenance model · Money, units and time · Object reference
Guides — Guide: search · Guide: price history · Guide: are these the same product? · Guide: making a purchase decision · Guide: delivery is a function of place and time · Guide: trust, risk and when not to buy · Guide: watches and alerts · Guide: agent memory · Guide: matching your catalogue · Guide: bulk export
Using the API — Pagination · Filtering and sorting · Field selection · Rate limits · Errors · Idempotency · Caching
Events — Receiving webhooks · Verifying webhooks · Event reference
Operations — Versioning · Changelog · Status, freshness and support · Migrating from another provider