- A
vsk_test_key emails only addresses you have verified on Test recipients, plus the members of your organisation whose sign-in address has been verified. A send to anybody else is refused — it is not silently dropped. An address is verified by its own mailbox: it is emailed a link, and the person who opens it presses a button to agree. The link works for 7 days; add the address again to send a fresh one. - It is never billed and never counts against your plan’s envelope allowance.
- It sends no text and no WhatsApp message. A recipient asked for a code on their phone sees the code on the signing screen, inside the test notice, instead of being sent it, and nothing counts against your plan’s mobile codes. See signer verification.
- What it produces is a watermarked sandbox document that binds nobody. Nothing signed with a test key is legally valid. It is a real sealed PDF — so your verification code has something to run against — sealed by a certificate issued for the sandbox and for nothing else, and that certificate is what says the document binds no one.
- It reaches every endpoint a live key does, at the same rate limit, except one kind of act that would change what live envelopes contain: renaming a template’s fields and changing where a brand’s signing pages may be framed. That needs a live key.
- A
vsk_live_key is the opposite of all three. The two are separate credentials; the environment is inside the hashed value, so a test secret cannot be re-presented under a live prefix.
A test sent from the dashboard
The dashboard’s Send step has a Send as a test switch. With it on, the envelope goes out as exactly the sandbox envelope a test key sends, under the same rules: the same recipients only, not counted against your plan, watermarked and binding nobody. Its webhook events carry"sandbox": true, and the dashboard marks it Test wherever it is listed.
A draft can become a test envelope at the moment it is sent, and never the other way: an envelope
a test key created always goes out as a test, whoever sends it.
Webhooks in each environment
Every webhook endpoint says which events it receives inenvironment:
An endpoint you register with an API key starts in that key’s environment, so a
vsk_test_ key
registers a test endpoint. Name environment in the request to choose. Endpoints registered before
this setting existed receive both. Change it with
PATCH /api/v1/webhooks/{webhookId}, or under Settings ›
Webhooks. A change applies to the next event; a delivery already queued is still sent.
An event about a template, such as a finished naming run, belongs to neither environment, because a
template serves test and live sends alike. It reaches every webhook endpoint whatever its setting.
Every body still carries sandbox. On an endpoint that receives both, it is how you tell them apart.
See Webhooks.