Environments
Casap runs the Disputes API in two environments you can reach. They share an API and nothing else.
| Environment | Base URL | Purpose |
|---|---|---|
| Sandbox | https://api-sandbox.casaphq.com |
Build and test. |
| Production | https://api.casaphq.com |
Live members, live disputes. |
Sandbox
Sandbox runs on synthetic members and transactions that Casap seeds, or on your own test environment; Casap supports both. It has the same API surface and validation rules as production, so a request that works there works in production unchanged.
Nothing done in sandbox moves money. Sandbox does not file with a card network unless Casap enables test filing for your organization; by default the dispute runs through the same states without leaving Casap.
Production
Disputes created in production are real. Casap files with the network where the rail allows, asks your systems for credits and card replacements, and the regulatory clocks run from the moment the dispute is created.
What is issued per environment
Each environment has its own credential, its own webhook endpoint registration, and its own webhook signing secret. None of them crosses: a sandbox API key presented to production is refused with 401, a signed token must carry the audience value issued for the environment it calls, and a production webhook secret does not verify a sandbox message. See Authentication and Getting set up.
Going live
Receive production credentials
Casap issues the production credential and registers your production webhook endpoint and signing secret.
Switch the base URL and the credential
Change api-sandbox.casaphq.com to api.casaphq.com and load the production credential.
Verify a production webhook
Confirm your endpoint verifies a signature with the production secret before the first real dispute arrives.