Skip to main content
This guide takes you from zero to a successful authenticated request against the Atlas API.
While the custom domain is being set up, the API is served from https://api-atlaswork.vercel.app. Endpoints are mounted under /api.

​
1. Get an API key

API keys are created and revoked from the dashboard. A key is shown in full exactly once, at creation — store it somewhere safe. A new account starts with a free credit grant, so you can create, review, and send a real envelope before entering any payment details.

​
2. Make an authenticated request

Every /api/v1 request carries your API key as a bearer token (the x-api-key header also works). Start with the authenticated ping endpoint, which proves your key is valid: 
curl https://api-atlaswork.vercel.app/api/v1/ping \
  -H "Authorization: Bearer $ATLAS_API_KEY"
A valid key returns: 
{ "pong": true }
A missing or invalid key returns 401 with the standard error envelope: 
{ "code": "unauthorized", "message": "Missing or invalid API key" }

​
3. Explore the API

Browse the full, always-current surface in the API reference — it’s generated from the live OpenAPI document, so it never drifts from the running API.

​
Next steps

Authentication

API keys, signer tokens, and the one-method-per-prefix rule.

Idempotency

Make retries safe on every state-changing call.

Webhooks

Track the envelope lifecycle without polling.

MCP server

Drive signing from an AI agent.