API sandbox

Build your integration on sample data.

A test key calls the same endpoints as your live key and gets the same response format. It spends no credits and creates nothing in your account, so you can rerun your code while you debug.

Get your test key Read the sandbox docs →

Demo key: pc_test_demo
Every documented endpoint
60 requests a minute
Live error bodies on request

try-the-sandbox.sh

# no account needed, no credits spent
curl https://app.pipecorn.com/api/v2/contacts/single_enrich \
  -H "X-API-KEY: pc_test_demo" \
  -H "Content-Type: application/json" \
  -d '{"firstname": "Emily", "lastname": "Carter",
       "domain": "northwind-analytics.example",
       "enrichment_type": ["email", "phone"]}'

# → 200 OK, Pipecorn-Mode: test
{
  "enrichment_id": "9d8c7b6a-5f4e-4d3c-…",
  "first_name": "Emily",
  "last_name": "Carter",
  "status": "pending",  0 credits
  "status_url": "…/contacts/9d8c7b6a-…"
}

What a test key does

Try every endpoint before you spend a credit.

Your test key is on Settings › API keys, next to your live key. Every response to it carries the header Pipecorn-Mode: test.

No credits spent

Enrichments, lookups and extractions cost nothing and use none of your plan quota.

Credits

Sample data in the live format

Invented people and companies on the reserved .example domain, in the shape production returns.

Data

Nothing is created

No search, list or enrichment is created, nothing is sent to LinkedIn and no webhook fires.

Account

Errors on request

Send Pipecorn-Sandbox-Status: 402 and you get the insufficient-credits body the live API sends.

Errors

Error handling

Ask for an error and get the real body.

Pipecorn-Sandbox-Status

Send 400, 401, 402, 403, 404, 409, 422 or 429 and the sandbox answers with that status and the body the live API sends for it. A 409 or a 429 also carries Retry-After.

FAQ

Sandbox questions, answered.

What developers ask before they swap in a live key. Anything missing? We reply within 24h.

Book a demo

Is there a sandbox or an SDK?

Yes, there is a sandbox. A test key calls every API endpoint and returns sample data in the live format, without spending credits or changing anything in your account, and the public key pc_test_demo works before you sign up. The API is plain REST and needs no SDK, and agents connect through the MCP server at mcp.pipecorn.com/mcp.

What doesn't the sandbox do?

It answers each endpoint with the same sample whatever you send, so it doesn't check your parameters or remember what you created. No webhook is sent and no background job runs. To test your error handling, send the Pipecorn-Sandbox-Status header with a status such as 402 or 429 and you get the body the live API sends.

How do I move from the sandbox to production?

Replace the test key with your live key or your workspace key. The endpoints, parameters and response format stay the same. Responses stop carrying the Pipecorn-Mode: test header, and calls start spending credits from your balance.

How do I get an API key?

Every plan includes API access, the Free plan too. Grab your key from Settings → API in the dashboard. Keys are scoped per workspace, and you can rotate them at any time.

Do API and MCP calls use the same credits as the app?

Yes. The app, the API and MCP share one wallet. A verified email costs 3 credits and a mobile 30, and bounces, dead numbers and misses cost nothing whichever channel you call from.

Ready for real data?

Create a free account, keep your test key for development and use your live key in production.