PriceTracker

PriceTracker API reference

Use API keys only from your backend. This reference never asks for, stores or sends credentials.

Consumer workflow: upsert a product, replace your subscription with the required market and delivery contexts, then read prices in batches. Use snapshot.updated to synchronize caches. Operator-only routes require the admin scope.

From a game to a price

  1. Identify the copy. Reuse an existing product or upsert its stable slug with products:write. Keep platform, region, edition and completeness distinct.
  2. Subscribe to tracking. Use PUT /v1/subscriptions/products/{product} with tracking:write and the marketplace/delivery contexts your consumer needs.
  3. Read prices. Use POST /v1/products/asking/batch with read. A new product may be waiting for its first capture; missing prices are not zero.
  4. Stay synchronized. Subscribe to snapshot.updated with webhooks:write, verify signed raw request bodies on your server, and reconcile periodically.

Examples below are generated from the contract, not live results. Replace placeholders and check required fields before using them. No requests can be executed from this page.

Loading the server's OpenAPI contract…