API Tokens
API tokens provide programmatic access to the gateway for CI/CD pipelines and automation.
Viewing Tokens
Section titled “Viewing Tokens”Navigate to API Tokens in the sidebar to see all tokens:
| Column | Description |
|---|---|
| Token ID | Public UUID for the token |
| Name | Descriptive name |
| Status | Active or expired |
| Created By | User who created the token |
| Last Used | Most recent API call using this token |
| Created | When the token was created |
Creating a Token
Section titled “Creating a Token”- Click Create Token
- Enter a descriptive name
- Choose permissions (or use a role shortcut like Viewer, Ops, Deployer, CI/CD, Admin)
- Click Create
- Copy the token secret immediately
Token Format
Section titled “Token Format”Tokens are prefixed with rgw_:
rgw_xxxxxxxxxxxxxxxxxxxxx
The token string does not encode the role; permissions are stored server-side.
Using Tokens
Section titled “Using Tokens”Rack Gateway CLI
Section titled “Rack Gateway CLI”export RACK_GATEWAY_API_TOKEN="rgw_..."export RACK_GATEWAY_URL="https://gateway.example.com"
rack-gateway appsrack-gateway deploy -a myappDirect API Call
Section titled “Direct API Call”curl -H "Authorization: Bearer rgw_..." \ https://gateway.example.com/api/v1/rack-proxy/appsEditing or Deleting Tokens
Section titled “Editing or Deleting Tokens”- Edit lets admins (or deployers who own the token) update name and permissions.
- Delete Token permanently removes the token.
Best Practices
Section titled “Best Practices”- Use CI/CD role shortcuts for automation tokens
- Rotate tokens regularly
- Delete unused tokens
Related
Section titled “Related”- CLI Authentication - Token usage in CLI
- Deploy Approvals - CI/CD workflow