Skip to main content
The Exchanges Data service exposes JSON endpoints for CORE3 exchange intelligence: aggregate and per-exchange Probability of Loss (PoL), ratings, transparency and solvency sections, listed assets, and search. Public traffic reaches it through the CORE3 API gateway, which mounts the service under the exchanges_data path prefix (mirroring how Projects Data API uses projects_data).
If you’re interested in our API, feel free to reach out via [email protected]

​
Base URL

All paths in the machine-readable specification are relative to the gateway mount:
Append the versioned route from the spec (for example /v1/...). Example call for an exchange PoL history chart over the last 30 days:
Here binance is the {slug} path parameter for the exchange; pol is a fixed segment in the route (PoL score).

​
Authentication

Every request must include a valid API key in the x-api-key header. Keys issued for this API begin with the prefix core3_.
Do not embed keys in client-side public code. Prefer a backend or serverless proxy that adds the header.

​
Conventions

  • HTTP method: All documented operations use GET.
  • Version: Routes are under /v1.
  • {slug}: Exchange identifier in the path (examples in the spec use values like binance; use slugs returned by list, ratings, search, or dashboard routes).
  • History by range: PoL history endpoints that are not “chart” variants expect Unix timestamp bounds: required query parameters from and to (seconds).
  • History by chart window: Chart endpoints accept optional days (integer 1–365). Omit days for all-time history, as described in the spec.

​
Endpoint map

Path templates are shown without the gateway prefix; prepend https://api.core3.io/exchanges_data when you call the API.

​
Health

​
Exchanges

​
PoL score

​
Ratings

​
Errors and status codes

Follow HTTP semantics. The health endpoint documents 503 when checks fail; other routes return standard client and server errors according to gateway and service behavior.

​
Next steps

  • Use GET /v1/ratings/parameters (and /v1/ratings/parameters/tokens when filtering by listings) so ratings UI matches server-supported values.
  • For methodology context, see CEX PoL methodology and CEX PoL scoring logic.
If you’re interested in our API, feel free to reach out via [email protected]