Live and test
| Key prefix | Environment | Effect |
|---|---|---|
dbk_live_ |
live | Real data. An import creates real leads; pausing a campaign really stops it. |
dbk_test_ |
test | The sandbox, when it is switched on for your account. |
Live keys
Everything done with a live key has real effects on your account. Build and test your integration with read-only scopes first, and add write scopes when you are ready.
Test keys
Test keys work only when the sandbox is switched on for your account; until then a test key answers
401 invalid_api_key. In the sandbox, requests are answered from sample
data: nothing is written to your account and nobody is called, texted or messaged.
Each API client has its own sandbox. Two integrations of the same account see two separate sample data sets with different ids, so one never sees what another reads or creates. The same request always answers the same way, and writes are simulated: they answer what the live API would, and the sample data does not change.
What you can try in the sandbox (click-to-call, WhatsApp and a lead dialled at once answer 403
tier_not_enabled in the sandbox too, as live, until they are available; the rows below show how they
will answer then):
| To try | Send |
|---|---|
| A click-to-call that is accepted | POST /v1/calls with agent_extension 3901 (or agent_email [email protected]) |
An agent who is not ready (409 agent_unavailable) |
agent_extension 3902 |
A call refused by a compliance check (422 dial_refused) |
to +12125550198 |
A number on the Do-Not-Call list (422 on_dnc) |
to +12125550199 |
| A lead put first in the dialling order | POST /v1/leads on the running sample campaign with dial_now: true |
| A lead source | source: website, facebook or referral (anything else answers unknown_source) |
A refused duplicate message (409 duplicate_client_reference) |
the same client_reference twice |
GET /v1/me shows the environment of the key you are using (client.environment).