Data access controls
CloudConvert's access model is built around API keys generated in the dashboard rather than user roles or team-based permissions. Each key can be scoped to specific permissions, such as submitting and downloading tasks versus managing account settings, so an integration that only needs to run conversions doesn't have to hold a key with broader account access.
Practical Details
CloudConvert also offers sandbox API keys, which point to a separate sandbox environment for testing an integration without spending production credits or handling real files. For webhook notifications, payloads can be verified against a signing secret tied to your account -- worth doing since anyone who discovers your webhook URL could otherwise send a fake "job complete" callback.
Actionable Considerations
- Create a separate API key per integration or environment (for example, one for a Zapier scenario and a different one for a custom script), so a leaked key can be revoked without breaking every connected workflow.
- Scope each key to only the permissions it needs rather than issuing broadly privileged keys by default.
- Verify webhook signatures with the signing secret before trusting a completion notification, instead of assuming every POST to your endpoint is genuine.