Docs

Quickstart

Build your first integration

Set up a sandbox API key, make your first request, and follow the REST and MCP workflows.

Production and sandbox

Organization API keys are bound to one environment. Sandbox keys use the operations marked “Production and sandbox” in the API reference against isolated test data. Production-only operations, and the tools that map to them, are unavailable in sandbox; the sandbox has its own MCP server. Credentials are rejected outside their assigned environment, and the error names the right address. Limits, available operations, and retry testing: Sandbox and testing

Make your first authenticated request

Start with an isolated sandbox organization and a sandbox API key.

Open the developer console

Open /consola from Exac, select Test, and open API keys for your current workspace.

Create a sandbox API key

Create a key for Test and copy it once. Exac prepares the isolated environment automatically.

Verify the sandbox organization

Call GET /v1/organization with the sandbox key against the sandbox server shown in OpenAPI.

Run a Test workflow

Create a contact and CFDI draft, then create, retrieve, and cancel a test stamp. Sandbox artifacts are not submitted to SAT and have no fiscal validity.

curl "https://api.sandbox.exac.mx/v1/organization" \  --header "Authorization: Bearer <EXAC_API_KEY>"

Your first write

Every write requires an Idempotency-Key. Generate one key per operation and reuse it on each retry: after a timeout or a 429 or 5xx error, repeating the same request returns the original result instead of duplicating the effect.

curl -X POST "https://api.sandbox.exac.mx/v1/contacts" \  -H "Authorization: Bearer <EXAC_API_KEY>" \  -H "Idempotency-Key: sandbox-create-contact" \  -H "Content-Type: application/json" \  -d '{    "kind": "customer",    "legalName": "Estudio Jacaranda",    "email": "administracion@jacaranda.example",    "rfc": "AAA010101AAA",    "taxSystem": "601",    "cfdiUse": "G03",    "address": {      "postalCode": "82110",      "country": "MEX"    }  }'

Request, response, and retry conventions

Send Authorization: Bearer <credential> on every API request and Content-Type: application/json when sending a JSON body. JSON successes use { data }; paginated responses also include pagination. Failures use { error: { code, message, status, details? } }. Branch on error.code, not the human message. File downloads return bytes instead of a JSON envelope.

When you create an organization API key you choose its access level with accessLevel: full (the default) or read. A read key can call every REST operation and MCP tool that only reads data, and receives 403 on everything else, including API-key management. There are no custom per-operation scopes.

Canonical workflows

Use the same domain intent through REST or MCP. These examples are validated against the runtime contracts; replace example identifiers and credentials with values from your organization.