API version 1 and protection profiles
The Torzen team, April 27, 2026
Many teams build releases only on CI servers. Until now, the protected file had to be downloaded from the panel by hand. From today, on the Pipeline plan, the API handles that step.
Three requests
You upload a file with its symbols and settings, check the job status, and download the result when it is ready. API requests use the same daily limit as protections started in the panel, and their jobs go to the priority queue.
Tokens
You create a token in account settings and give it an expiry date. Each build server can have its own token, so a leaked token does not mean replacing all of them. Keep tokens in your CI system’s secrets, never in the repository.
Protection profiles
A profile is a named set of settings saved in the panel. In an API request you pass the profile name instead of sending a settings file with every release. Profiles work on every plan, in the panel as well.
The requests, error codes and a GitHub Actions example are in the API reference.