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.
CLI In this interface
4 steps Steps
3 interfaces Available in
Use this path when
Use the PAT revoke command when the terminal already has the credential id.
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. Run `./backlog.sh pat list` if you still need to find the credential id.
- 2. Run `./backlog.sh pat revoke cred_123`.
- 3. Confirm the JSON response reports success.
- 4. Delete the raw PAT from any external secrets store or environment variable that still holds it.
Keep Going in Sessions and Personal Tokens
Stay in the same interface and move to the next closest task in this topic when needed.
CLI 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
CLI 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
Nearby Guides
These guides stay close to the current workflow so you can keep moving without restarting discovery.