sondahub / Sandboxes
Sandboxes for the APIs you integrate
Stand-ins for real companies’ APIs that the official SDKs work against, given a new host and a few lines for the session — the same paths, errors and behaviour, callbacks signed the vendor’s way, and no account to open. Free, keyless, built for the integration you are writing now.
Independent imitations for testing. Not affiliated with, or endorsed by, the companies named.
The sandboxes
Stripe sandbox
A stand-in for Stripe’s API (online payments): customers, payment_methods, payment_intents, charges, refunds….
Twilio sandbox
A stand-in for Twilio’s API (SMS, voice calls and phone verification): Messages, Calls, IncomingPhoneNumbers, Accounts, Verify v2 Services, Verifications, VerificationCheck….
Import them
Each sandbox publishes an OpenAPI 3 document. In Sonda: Import → From a URL, paste the address, and the whole sandbox appears as a project — a folder per resource, a request per operation, example bodies and ids from the seed account.
| Sandbox | OpenAPI 3 | Auth |
|---|---|---|
| Stripe | https://api.sondahub.com/sandbox/stripe/openapi.json | Bearer sk_test_sondahub |
| Twilio | https://api.sondahub.com/sandbox/twilio/openapi.json | Basic: any Account SID (AC + 32 hex) and any token |
How they work
Same API, different host. The paths, parameters, form encoding, ids, list envelopes and error codes are the vendor’s, so the official SDK works once its host is swapped and a few lines carry the session token from one answer to the next. Credentials are made up: any Stripe test key, any Twilio Account SID.
Behaviour, not just shapes. A payment declines on the vendor’s own test cards, a message is delivered a few seconds after it is queued, a verification is approved by the right code — the flows your code has to handle.
Callbacks, signed their way. Webhooks and status callbacks go to your endpoint signed exactly as the vendor signs them, so the SDK’s own signature check can be proven against them.
State that travels with you. There is no database: what you create comes back in a session token, and the next request that carries it sees it. Nobody else sees your data; drop the token and the account is back to its seed.
Questions
What is a sandbox here?
An imitation of a real company’s API — the same paths, authentication, ids, errors and behaviour — that an official SDK can be pointed at by changing the host. It is for building and testing an integration before, or instead of, using the vendor’s own test environment.
Are these the vendors’ own test environments?
No. sondahub is not affiliated with, or endorsed by, any of these companies. Stripe and Twilio run their own test modes; these sandboxes are independent imitations with no account, no keys to apply for and no real money or messages.
Where is my data kept?
In the X-Sondahub-Session token each answer carries, like every write on sondahub — nothing on the server. Each page shows the few lines that make an SDK carry it.