Get Started
Authentication
Authenticate Atlas API requests with environment-specific API keys managed through the portal.
Atlas uses API keys for customer API access.
Header
Send your key in the X-API-Key header:
curl --request GET \
--url https://api.rangler.co/v1/filings \
--header "X-API-Key: atl_live_your_key_here"Key formats
| Environment | Prefix |
|---|---|
| Live | atl_live_ |
| Sandbox | atl_test_ |
Atlas keys are environment-specific. A live key cannot be used against sandbox, and a sandbox key cannot be used against live.
Where keys come from
Generate and revoke keys in portal.rangler.co.
The portal is the only supported human workflow for key management in the current customer offering.
Access model
- API keys belong to organizations, not individual developers
- usage is metered at the organization level
- keys should be stored in your own secret manager
- revoke unused keys instead of rotating shared credentials informally
Company-email access
Portal access is restricted to company emails. Personal mailbox domains are not accepted for customer onboarding.
Authentication failures
Atlas returns 401 Unauthorized when:
- the key is missing
- the key is invalid
- the key has been revoked
- the key is expired
- the key is used against the wrong environment
See Errors for the full response shape.