Test mode

Create a key with mode Test (it starts with cvio_test_) in your organization's Settings → API Keys tab. Test keys use exactly the same endpoints, validation, limits and job flow as live keys, so you can build and rehearse your whole integration before switching to a live key (cvio_live_…).

What differs

• No credits. A test job never holds or charges credits, whatever the conversion would normally cost. Your balance is unchanged afterwards.
• No real conversion. The "converted" file is a copy of the file you uploaded, renamed to the target extension. Use test mode to check the flow (upload, waiting, download, webhooks), not to check the output of a conversion.
• Marked as test. Every job has test_mode: true.
• Deterministic. The same input always gives the same result, and a test job finishes within about a second.

What is the same

• Creating, listing, cancelling and deleting jobs, single and multipart uploads, and import/url.
• Webhooks fire for test jobs as for live ones.
• Rate limits, scopes, idempotency, error codes, and the 24-hour result retention.
• Supported formats and file-size limits: a pair that is not supported is refused in test mode too.

Isolation

Test keys and live keys never see each other's jobs, even in the same organization. A leaked test key cannot cancel or delete anything made with a live key.