Clara provides a sandbox environment for testing your integration end-to-end without affecting real data or triggering real financial operations.
Sandbox Base URLs
The sandbox uses the same base domain as production, with /api-test/ instead of /api/ in the path:
| Market | Sandbox Base URL |
|---|
| Mexico | https://public-api.mx.clara.com/api-test/ |
| Brazil | https://public-api.br.clara.com/api-test/ |
| Colombia | https://public-api.co.clara.com/api-test/ |
Example
# Production
GET https://public-api.mx.clara.com/api/v3/transactions
# Sandbox
GET https://public-api.mx.clara.com/api-test/v3/transactions
Authentication in Sandbox
Authentication works identically to production — you still need a valid mTLS client certificate and a Bearer token obtained from the OAuth endpoint. Sandbox and production share the same auth flow.
curl --request GET \
"https://public-api.mx.clara.com/api-test/v3/transactions?page=0&size=10" \
--header "Authorization: Bearer <TOKEN>" \
--cert client.crt \
--key client.key
Getting Sandbox Credentials
Sandbox credentials are separate from production credentials. Contact your Clara integration team to request access:
What You Can Test
The sandbox supports the same endpoints as production. You can test:
- Card creation, configuration, lock/unlock, and deletion
- Transaction retrieval with filters and pagination
- User management
- Billing statement retrieval
- VCN lifecycle (create, update, cancel)
Differences from Production
| Behavior | Production | Sandbox |
|---|
| Financial operations | Real | Simulated — no real money moves |
| Card issuance | Physical cards are shipped | No physical fulfillment |
| Data | Your company’s live data | Isolated test data |
| Webhooks | Live events | May have delays or be unavailable |
Sandbox data is periodically reset. Do not build long-running dependencies on sandbox UUIDs or state — treat each test session as ephemeral.
