Documentation 40
Documentation · start here
Your first request, without the setup.
Point the client you already use at SandboxAPIs — any provider in the catalog — and your read code just works against a deep, real-looking data set (olympus-labs), not an empty test account. Read-only and API-identical (every dialect the real provider offers); adoption is a one-line base-URL swap, with no path prefixes and no custom routes.
01 / Pick a provider
25 hosts, all drop-in.
25 providers
git host4
issue tracker2
AI telemetry6
messaging2
CI/CD2
observability6
CRM/support3
02 / The guarantees
How it works.
- Exact mirror. Provider hosts serve provider paths exactly — same JSON, headers, status codes. Your existing client library works unchanged.
- Read-only. Writes return the provider's error shape with a friendly "this universe is read-only" message naming what was attempted.
- Coherent. Every reference resolves — a PR's author is a fetchable user, its commits exist with matching SHAs, on every provider alike.
- Deterministic. Pinned snapshots regenerate byte-identically, so CI never flakes on the data.
- Cheap to poll. Reads carry an
ETag, and a conditional request that returns 304 costs nothing when our CDN answers it from its shared cache.
03 / Import it instead
Collections for every host.
Every provider ships a Postman collection (v2.1, importable by Postman, Insomnia, Bruno and Hoppscotch) and a minimal OpenAPI 3.1 document, with our base URL and that provider's own auth header already set. Import, press send.
Both are generated from our coverage manifest — our own record of what these hosts answer — and never from a vendor's published specification, several of which their vendors do not licence for redistribution. So they list paths, methods and the answer each one gives, and carry no request or response schema. Each collection also holds one write, in a folder called "Read-only refusal, on purpose", so the read-only boundary is something you can press rather than read about.
04 / Next steps