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….
SendGrid sandbox
A stand-in for SendGrid’s API (transactional and marketing email): mail/send, Event Webhook (signed), messages (Email Activity), stats, suppressions and unsubscribe groups….
Authorize.net sandbox
A stand-in for Authorize.net’s API (card and eCheck payments): createTransaction (charge, authorize, capture, void, refund), Transaction Reporting and settled batches, Customer Information Manager (profiles, payment profiles, shipping addresses), Automated Recurring Billing, Accept (securePaymentContainer, the hosted payment form)….
OpenAI sandbox
A stand-in for OpenAI’s API (language models: chat, the Responses API, embeddings): chat/completions (streaming, n, tools, structured outputs, logprobs, reasoning tokens), responses (streaming events, function calls, previous_response_id, stored, background, input_items, input_tokens), embeddings (float and base64), moderations, models….
Anthropic sandbox
A stand-in for Anthropic’s API (the Claude API: messages, batches, models): messages (streaming, tools, extended and adaptive thinking with signatures, structured outputs, stop sequences), messages/count_tokens, prompt caching with cache_control breakpoints, messages/batches (results as JSONL), models.
Secrets managers
For the code that loads its configuration at boot, rotates a password, rolls a value back or reads a vault: stand-ins for the secrets managers your SDK or CLI already talks to, each with a seed of fake secrets — versions, labels, references, soft delete — and the vendor’s own sign-in where it has one. Never send them a real secret: they are public playgrounds, and what you write lives only in your session token.
AWS Secrets Manager sandbox
A stand-in for AWS Secrets Manager’s API (secrets with versions, rotation and replication): all 23 actions over JSON 1.1 with SigV4, versions and the AWSCURRENT / AWSPREVIOUS / AWSPENDING labels, ClientRequestToken idempotency, deletion with a recovery window, rotation (the sandbox plays the rotation function)….
Azure Key Vault sandbox
A stand-in for Azure Key Vault’s API (a vault’s secrets, behind Microsoft Entra ID): secrets and versions, the bearer challenge and an Entra ID token endpoint, content types, tags, enabled / nbf / exp, soft delete, recover and purge, backup and restore….
Google Secret Manager sandbox
A stand-in for Google Secret Manager’s API (secrets and versions in Google Cloud): secrets, global and regional, versions: ENABLED, DISABLED, DESTROYED, access with CRC32C checksums, aliases and latest, delayed destruction, expiry, rotation settings….
1Password Connect sandbox
A stand-in for 1Password Connect’s API (vaults and items from a Connect server): vaults, items of every category: fields, sections, URLs, tags, generated passwords from a recipe, one-time-password fields with the current code, files and their content….
Doppler sandbox
A stand-in for Doppler’s API (projects, configs and secrets for every environment): projects, environments, root and branch configs, secrets with raw and computed values (references resolved), downloads in json, env, yaml, docker and dotnet-json, visibility, value types, notes, config logs and rollback….
Infisical sandbox
A stand-in for Infisical’s API (projects, environments, folders and secrets): Universal Auth login, renew, revoke, secrets through the raw v3 and the v4 API, single and batch, ${KEY} and ${env.folder.KEY} references, folders and secret imports, tags, versions, personal overrides….
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 |
| SendGrid | https://api.sondahub.com/sandbox/sendgrid/openapi.json | Bearer SG.sondahub-sandbox |
| Authorize.net | https://api.sondahub.com/sandbox/authorizenet/openapi.json | In each body (filled in): sondahub / SandboxKey123456; Basic with the same for webhooks |
| OpenAI | https://api.sondahub.com/sandbox/openai/openapi.json | Bearer sk-sondahub (any sk- key) |
| Anthropic | https://api.sondahub.com/sandbox/anthropic/openapi.json | x-api-key: sk-ant-sondahub (any sk-ant- key) |
| AWS Secrets Manager | https://api.sondahub.com/sandbox/aws-secrets-manager/openapi.json | AWS SigV4, service secretsmanager: AKIASONDAHUB000001 / probe-secret |
| Azure Key Vault | https://api.sondahub.com/sandbox/azure-key-vault/openapi.json | Bearer: any token (after Key Vault’s challenge) |
| Google Secret Manager | https://api.sondahub.com/sandbox/google-secret-manager/openapi.json | Bearer: any token |
| 1Password Connect | https://api.sondahub.com/sandbox/1password-connect/openapi.json | Bearer sondahub-connect-token (any token) |
| Doppler | https://api.sondahub.com/sandbox/doppler/openapi.json | Bearer dp.pt.sondahubSandboxPersonalToken (any dp.pt. or dp.st. token) |
| Infisical | https://api.sondahub.com/sandbox/infisical/openapi.json | Bearer: the Universal Auth access token (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, any SendGrid key that starts with SG., any Authorize.net login with a 16-character key, any OpenAI key that starts with sk-, any Anthropic key that starts with sk-ant-, any AWS access key (the published one has its signature checked), any bearer token for Key Vault, Secret Manager, Connect and Infisical, any Doppler token.
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, an email bounces and lands on the bounce list, a capture settles and can be refunded — the flows your code has to handle.
A model that follows a script. The OpenAI and Anthropic sandboxes answer with a scripted model: no tokens are bought and the same request always gets the same answer, so a test of your streaming, tool loop or retry code passes or fails for your code’s reasons, not the model’s. A phrase in the message — [[tool]], [[refuse]], [[error:429]], [[break]] — picks the outcome you want 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, SendGrid its sandbox mode and Authorize.net its sandbox accounts, and OpenAI and Anthropic bill every call; these sandboxes are independent imitations with no account, no keys to apply for and no real money, messages, email, model or secrets.
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.