APEXON API PLATFORM

CatalogAIO API documentation

Amazon catalog data behind one clean REST surface: product details, offers, reviews, search, suggestions, and best sellers across 22 storefronts — plus drop-in path aliases for popular marketplace Amazon APIs.

https://catalog.apexon.dev

• Interactive explorer — Swagger UI at catalog.apexon.dev/docs, ReDoc at catalog.apexon.dev/redoc.
• Machine-readable spec — OpenAPI at catalog.apexon.dev/openapi.json for generating clients, mocks, and tests.
• 22 storefronts — pick a market per request with domain=amazon.de or country=DE; see Storefronts.
• Drop-in aliases — OpenWeb/Axesso-style and Scout-style paths answer alongside the native /v1 surface.

Quickstart

Grab a key (subscribe on the marketplace, or request a direct key), then make your first calls. Health is public; everything else needs the key.

curl https://catalog.apexon.dev/health

curl https://catalog.apexon.dev/v1/markets \
  -H "X-API-Key: $CATALOGAIO_KEY"

curl "https://catalog.apexon.dev/v1/product/B08N5WRWNW?domain=amazon.de" \
  -H "X-API-Key: $CATALOGAIO_KEY"

curl "https://catalog.apexon.dev/v1/search?query=wireless+earbuds&page=1" \
  -H "X-API-Key: $CATALOGAIO_KEY"

curl https://catalog.apexon.dev/v1/product/B08N5WRWNW/offers \
  -H "X-API-Key: $CATALOGAIO_KEY"

{
  "success": true,
  "data": { … },
  "request_id": "9f3c1a2b8d4e"
}

Every response also carries X-Request-Id, X-Cache, and X-RateLimit-* headers — see Responses & headers.

Authentication

CatalogAIO issues its own keys, prefixed ca_live_. Keys are product-scoped: a FinMarkets fm_live_ or LineSnap ls_ key will not authenticate here, and vice versa. Send a key any of these ways — first match wins:

Gateway traffic is verified by the platform: RapidAPI injects X-RapidAPI-Proxy-Secret alongside your X-RapidAPI-Key, and the secret is what vouches for the request. The rules, exactly as enforced:

• A valid direct key always works — with or without gateway headers present.
• Wrong proxy secret → 403 — presenting an X-RapidAPI-Proxy-Secret that does not match is rejected as forbidden.
• Rapid key without the secret → 401 — an X-RapidAPI-Key arriving outside the gateway (no valid proxy secret) is unauthorized.

Meta routes (/, /health, /legal/*, /docs, /redoc, /openapi.json) are public; /metrics is operator-only — it 403s without a valid metrics token or API key; every data route requires a key.

Responses & headers

Unlike FinMarkets' upstream-shaped pass-through, CatalogAIO wraps every successful response in a stable envelope — the payload lives under data and the shape per endpoint is visible in the interactive explorer:

{
  "success": true,
  "data": { … endpoint payload … },
  "request_id": "9f3c1a2b8d4e"
}

Standard headers

Errors

Errors always return the same machine-readable envelope — never an HTML error page:

{
  "success": false,
  "error": {
    "code": "rate_limited",
    "message": "Rate limit exceeded",
    "status": 429,
    "retry_after_seconds": 18
  },
  "request_id": "9f3c1a2b8d4e"
}

Rate limits & plans

Plans cap both monthly volume and burst rate. Requests-per-minute is enforced live and surfaced via X-RateLimit-*; the monthly quota resets at the start of each calendar month. A 429 tells you which limit you hit via error.details.limit_type. Core covers search, product details, autocomplete and markets; offers, reviews and best sellers require PRO or above and otherwise return 403 plan_upgrade_required.

Caching & freshness

Successful GET responses are cached server-side so repeat calls skip the storefront round-trip entirely. Cache windows are tuned per route family — offers and search refresh on the shortest intervals; product details and reviews a little longer; best sellers longest. The X-Cache header on every response tells you whether you got a cached copy.

Data is collected from publicly reachable catalog pages on a best-effort basis; it may be incomplete, delayed, or unavailable without notice, and it is not commercial advice.

Storefronts

Every data endpoint accepts domain= (e.g. amazon.de) or country= (e.g. DE) per request — no account-level region setting. Country codes are normalized: uk is accepted and mapped to gb / amazon.co.uk, and common aliases like usa→us and irl→ie work too. GET /v1/markets returns this list with aliases and marketplace ids.

Endpoint reference

The native surface lives under /v1. Path parameters are shown in braces; query parameters list their defaults where one exists. Full request/response schemas are in the interactive explorer.

Meta

Search & discovery

Products

Markets

Marketplace aliases

If you are swapping in from an OpenWeb/Axesso-style Amazon data API, these paths answer with the same engine, envelope, auth, and headers. They take country instead of domain (default US) and pass the ASIN as a query parameter.

Scout-style aliases

Scout-shaped paths for drop-in swaps. These serve the US storefront.