GET /api/v1/developer/pricecharting/

Same pricing bundle as Developer Pricing, but takes a PriceCharting numeric product ID instead of a Coda catalog key. The server resolves the catalog key internally.

---

Request

GET /api/v1/developer/pricecharting/{pricecharting_id}
X-API-Key: your_api_key

Path parameters

Parameter	Example	Description
pricecharting_id	2513024	PriceCharting's numeric product ID

Query parameters

Same as Developer Pricing (window_hours, outlier_stddevs).

Example

curl "https://api.coda-tech.net/api/v1/developer/pricecharting/2513024" \
  -H "X-API-Key: your_api_key"

---

Response 200

Same as Developer Pricing, with an added top-level id field:

{
  "id": "2513024",
  "product_key": "pokemon-sws07-umbreon-vmax-alt-art-secret",
  "window_hours": 24,
  "ungraded": { "..." : "..." },
  "graded": { "..." : "..." },
  "metadata": { "..." : "..." }
}

---

Resolution logic

1. Call the upstream pricing API with the given ID to fetch product metadata.
2. If the upstream returns 200: extract product_key from the catalog via ID mapping.
3. If the upstream returns 404 or 410: fall back to the local catalog map. If a known mapping exists, pricing continues from Coda's own observation database.
4. Run the same TWAP bundle as /developer/pricing/{product_key}.

Upstream resilience

If a product ID is deprecated upstream, the API still returns pricing for any product with a known local mapping.

---

Errors

HTTP	When
401	Missing or invalid API key
400	No catalog mapping found for this ID
502	Upstream error with no local fallback available
503	Upstream data source not configured on server