Overview
One subscription, one API key, a catalog of production-ready data APIs with consistent schemas.
Welcome. This platform gives you a catalog of data APIs behind a single subscription and a single API key — with the operational guarantees you would otherwise have to build yourself: consistent schemas, automatic failure recovery, transparent limits and predictable errors.
Base URL
All APIs share one base URL and are versioned in the path:
https://api.endpointry.com/v1/{api}/{endpoint}The machine-readable OpenAPI 3 specification for the entire platform is published at
/v1/openapi.json
and is generated from the same schemas the gateway enforces at runtime — it cannot drift from actual behavior.
The response envelope
Every successful response has the same shape. data carries pure content; meta is the
platform layer and speaks one language across every API:
{
"data": { "…": "endpoint-specific payload" },
"meta": {
"request_id": "req_7729f93d3facf68ff83e5c50",
"as_of": "2026-07-31T12:00:00.000Z",
"pagination": { "next_cursor": "…", "limit": 25, "returned": 25 },
"warnings": []
}
}request_id— always present; quote it in support requests.as_of— when this snapshot of the data was taken (UTC).pagination— present on list endpoints; see Pagination.warnings— non-fatal notices (for example, a field scheduled for removal). Absent when there is nothing to say; never required reading for a successful integration.
Errors follow RFC 9457 application/problem+json with
stable machine-readable codes — see Errors.
Where to go next
- Quickstart — first call in five minutes
- Authentication — how API keys work
- Rate limits & quotas — plan limits and response headers
- API reference — endpoints, schemas and examples