Sandbox & testing

Every account gets a sandbox alongside production. Use a test key (qsk_test_…) and your calls run against a simulated environment:

• No real documents are created, no emails are sent, nothing is charged.
• No quota is consumed — hammer it as much as you like while building.
• For supported simulated calls, request and response shapes match production.

The Playground in the Developer portal fires real requests with your test key so you can explore endpoints interactively before writing a line of code.

The hosted USB DSC flow needs a physical token and local QSign Agent. The separate /api/v1/sandbox/mock-dsc/ endpoints simulate handoff with a self-signed test certificate; they do not validate the production envelope flow, token or driver. See Hosted USB DSC API for the production sequence.

Tip

For supported simulated calls, switch to production with a qsk_live_… key in the X-Api-Key header. Hardware DSC requires the production Envelope API flow.