Manage API Keys
To call the platform through its API, create a key here first. Open the “API Keys” tab on the workbench “Settings / Personal Center” page.
The “Get API Key” button on the developers page brings you to the same place.
An API key belongs to the team you own, not to you personally. Usage from that key is charged to that team.
If you do not own a team yet, create is disabled and the page explains that there is no managed team.
Creating a key
Enter a recognizable key name and select “Create.” The button stays disabled while the name is empty.
On success the page shows the full key, and shows it only once. Copy it somewhere safe immediately.
Once you close or reload the page the full value is gone for good — the list only ever shows a prefix plus a mask. At that point your only option is to delete the key and create a new one.
A copy button sits next to the key; one click puts it on your clipboard.
The key list
Existing keys are listed below, each showing:
- The key name
- A prefix plus a mask (never the full key)
- Its status: Active or Disabled
When no key exists yet, the page prompts you to create one above.
Deleting a key
Each key has a delete button on the right. Deletion asks for confirmation first.
Deletion cannot be undone. Anything still using that key stops working immediately, so confirm nothing depends on it first.
Replace a key and troubleshoot API access
To replace a key, create a new one with a name that identifies its purpose. Update the caller's server-side configuration and confirm a successful request before deleting the old key. Keep a working key available while checking the replacement.
The masked value in the list cannot authenticate API calls. If you did not save the full value, create a replacement; the page has no way to restore the original full key.
For authentication or allowance errors, check that you are using the full key, that it still exists and has an available status, and that its team has sufficient credits. Also check the endpoint requirements. Switching the Workbench's current team does not change an existing key's ownership.
Keep the full key in server-side configuration or secure credential storage. Do not embed it in browser code, public repositories, or shared screenshots. Provide only the key name, prefix, and error details when contacting support.