Everything you need, built in.
The essentials for teams that want to move fast without giving up control.
One spec. Four SDKs. Zero drift.
Every SDK is generated from our OpenAPI 3.1 spec on every release. If it's in the API, it's in the SDK. If the API adds a field, your client gets it the day you upgrade.
- OpenAPI 3.1 spec published at `spec.atlas.dev`
- SDKs regenerated on every tagged API release
- Matching version number across all 4 SDKs
- Community SDKs (Elixir, PHP, Rust) use the same spec
Production-grade defaults.
Every SDK retries 429s and 5xxs with exponential backoff. POSTs get auto-injected idempotency keys. Request IDs surface on every response for support tickets.
- Exponential backoff with jitter — 3 retries by default
- Auto idempotency keys on POST/PUT
- Request IDs on every response and exception
- Pluggable HTTP client for observability hooks
Teams ship revenue with this.
Real-world use cases across every revenue function.
Frequently asked questions
Are there community SDKs?
Yes — Elixir, PHP, and Rust community SDKs are linked from the docs. They use the same OpenAPI spec but are maintained by contributors.
What runtime do the SDKs require?
Node 18+, Python 3.9+, Go 1.21+, Ruby 3.0+. Node SDK is ESM-first with CJS fallback and works in Cloudflare Workers and Deno.
How are releases versioned?
Calendar versioning on the API (e.g. `2026-01-15`). SDK patch versions track bugfixes; minor versions add new endpoints; major versions track API version bumps.
Can I contribute?
Yes — SDKs are on GitHub at `atlas-dev/atlas-<lang>`. File issues, submit PRs, or ping the DevRel team in Discord.