Sandbox
The Doc E Sign sandbox is the staging environment at doc-e-sign-staging. Use it to test the full signing flow end-to-end without touching production data.
API key authentication is not yet available. The sandbox currently uses session cookie authentication. This page will be updated when API keys launch in Phase 2.
Access the sandbox
- Go to staging.doc-e-sign.com/sign-in
- Enter your email address to receive a sign-in link
- Click the link to sign in
Use a real email address — the sandbox sends real emails via the same provider as production.
Get your session cookie
- Sign in to staging.doc-e-sign.com
- Open DevTools → Application → Cookies →
staging.doc-e-sign.com - Copy the value of
sb-access-token
This is your session cookie. It expires after one hour. Repeat the sign-in flow to get a fresh cookie when it expires.
Complete a full signing ceremony in under 5 minutes
The following curl sequence walks through the complete flow: upload → create envelope → sign → verify.
Replace <COOKIE> with your session cookie value throughout.
1 — Upload a PDF
curl -X POST https://staging.doc-e-sign.com/api/v1/upload \
-H "Content-Type: application/pdf" \
-H "Cookie: sb-access-token=<COOKIE>" \
--data-binary @your-document.pdf
Save the storagePath from the response.
2 — Create an envelope
curl -X POST https://staging.doc-e-sign.com/api/v1/envelopes \
-H "Content-Type: application/json" \
-H "Cookie: sb-access-token=<COOKIE>" \
-d '{
"title": "Sandbox test",
"signerEmail": "[email protected]",
"storagePathTemp": "<storagePath from step 1>",
"signingExpiresAfter": "1_day"
}'
Save the envelopeId from the response. A signing invitation email is sent immediately to signerEmail.
3 — Complete signing
Check your email for the signing invitation. Open the link and complete the signing ceremony — review, consent, type your name, submit.
4 — List envelopes to confirm completion
curl https://staging.doc-e-sign.com/api/v1/envelopes \
-H "Cookie: sb-access-token=<COOKIE>"
The envelope status should progress from sent → sealing → completed within a few seconds of submitting the signature.
5 — Verify the completed document
Once the envelope is completed, retrieve the Signing chain fingerprint from the completed PDF (printed on the audit page), then:
curl "https://staging.doc-e-sign.com/api/v1/verify?hash=<signing-chain-fingerprint>"
A "valid": true response confirms the document is authentic and unaltered.
Sandbox behaviour
- The sandbox environment behaves identically to production
- Signed PDFs produced in the sandbox are real, verifiable documents
- Data in the sandbox is cleared periodically — do not use it for production documents
- The sandbox Stripe integration uses test mode — no real charges are made
- Use Stripe test card
4242 4242 4242 4242(any future expiry, any CVV) if a billing flow is triggered
Differences from production
| Sandbox | Production | |
|---|---|---|
| URL | staging.doc-e-sign.com | doc-e-sign.com |
| Emails | Real emails sent | Real emails sent |
| Stripe | Test mode | Live mode |
| Data retention | Periodic wipe | Standard retention policy |