APEXON API PLATFORM

Documentation

Every Apexon product speaks the same dialect: the same auth header, the same error envelope, the same rate-limit headers. Learn the conventions once, then read the reference for whichever product you subscribed to.

Music, Web Tools, and Geo are planned; their endpoints are illustrative until they ship.

Coming from another Yahoo Finance API? Migrating from Yahu Financials — the paths are identical, so it is a base URL and a key.

What every product shares

These hold across the whole platform, so client code written against one product mostly works against the next.

• Auth header — X-API-Key: <key> on every request, with Authorization: Bearer accepted as an alternative.
• Rate-limit headers — X-RateLimit-* on responses, and 429 with Retry-After when you exceed your plan.
• Machine-readable errors — a stable JSON envelope with a code you can branch on. Never an HTML error page. Success bodies are product-shaped: FinMarkets passes the upstream payload through as-is, while CatalogAIO wraps data in a success/data envelope — see each reference.
• Interactive explorer — every product serves Swagger UI and an OpenAPI 3.1 document at its own host.

Keys and base URLs are per product

Each product issues its own key and answers on its own host. A FinMarkets key will not authenticate against LineSnap. The mechanism is identical, so adding a second product is a base URL and a key — not a new integration.

Plans are per product too — see each product's reference for its quota and rate-limit shape.