Testing
Try Sign in a sandbox environment before anyone signs for real: requests work end to end on the real signing page, with a few differences.
Requests made with a sandbox (coss_test_…) key work end to end: sessions open the real signing
page, signers sign, and the request is sealed and completed. What's different:
- No emails reach anyone. Invitations, reminders and copies go through the sandbox's fake provider: read them in the dashboard's emails page instead.
- The signing page says it's a test ("signing it has no legal effect"), and so does the certificate.
- The seal is a test seal. The completed PDF is sealed and verifies, but with a self-signed certificate ("coss.com Sign (sandbox test seal)"), so PDF readers like Acrobat show the signature as not trusted. Live requests are sealed with coss.com's trusted certificate.
- Nothing is billed, and sandbox requests don't count against the Free plan's requests.
allowed_originscan includehttp://localhostfor embedding while you develop.
Test PDFs need nothing special; put anchors like {{signature:signer_1}} in them to place fields
without coordinates. Webhooks (sign_request.*) are delivered as in live environments, and
coss trigger sign_request.completed sends a sample one.
Last updated