> ## Documentation Index
> Fetch the complete documentation index at: https://docs.get2dial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Testing without a sandbox

> Get2Dial has no sandbox or test mode — how to develop against the API without placing unwanted real calls.

Get2Dial doesn't have a sandbox, test mode, or dry-run flag — every API call against your
workspace is a real call against your real telephony configuration.

## How it works

There's no separate test environment and no reserved test phone numbers that skip actually
dialing. An originate call, once it reaches a connected carrier, is a real phone call.

## When to use it

Most API development doesn't touch origination at all — building and testing against
[campaigns](/developers/recipes/push-leads-into-a-campaign), [CDRs](/developers/recipes/sync-cdrs-to-your-warehouse),
and [webhooks](/developers/recipes/react-to-call-events) doesn't place a single call. Where
you do need to exercise real dialing, do it deliberately:

* Use a workspace or campaign set up specifically for testing, not a production one.
* Dial numbers you control — your own mobile number, a colleague's extension — never a real
  customer or lead number.
* Keep test campaigns paused except when you're actively testing, so nothing dials
  unattended.

## What it affects

Every test call still goes through your real carrier and is billed the same as any other
call — there's no separate free tier for development traffic.

## Next steps

<CardGroup cols={2}>
  <Card title="React to call events" href="/developers/recipes/react-to-call-events" />

  <Card title="Production checklist" href="/developers/production-checklist" />
</CardGroup>