Revoke a Personal Access Token
Revoke a human-owned API key by credential id when it is obsolete, leaked, or no longer appropriate for the workflow.
API In this interface
4 steps Steps
3 interfaces Available in
Use this path when
The revoke endpoint deletes the PAT by credential id for the current human principal.
What you'll finish here
- Find the right credential id first.
- Use the correct revoke surface.
- Confirm the key should no longer be used anywhere.
Where this happens
Same Task, Other Interfaces
Use the version that matches where you are working now. The subject matter stays the same; the delivery changes by surface.
Do the work
- 1. List the current PATs first if you do not already know the credential id.
- 2. Send the revoke request using the credential id in the path.
- 3. Wait for the success response.
- 4. Delete the raw token anywhere it may still be stored.
Keep Going in Sessions and Personal Tokens
Stay in the same interface and move to the next closest task in this topic when needed.
API Sessions and Personal Tokens
List Personal Access Tokens
Review the current personal API keys before creating a new one or revoking an old one.
4 steps
API Sessions and Personal Tokens
Create a Personal Access Token
Create a human-owned API key with the narrowest useful scope set and store it safely because the raw token is only shown once.
4 steps ยท 1 examples
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.