Console API — Keys
API-key lifecycle for a Triport account: create, list, rotate and revoke keys, read per-key endpoints and usage.
- Method / Endpoint
https://triport.io/v1/keys/…- Network
- — (account-level)
- Authentication
- Console session — see session model
- Tier / rate limit
- Account-level; not metered against chain RPS budgets
What this section covers
Automate what the API Keys tab does by hand: mint a key from CI, list existing ones, rotate a compromised key without downtime, or revoke it. Each key exposes its chain endpoints and a usage breakdown by method and day, so quota dashboards can be built on top.
The endpoint list is below; every page carries the request/response schema, error envelope and a runnable example. Part of the Console API.
POST Create an API key
Mint a new API key for your account and receive its secret value — returned exactly once, at creation time.
GET Get key endpoints
Return the per-chain connection endpoints a given API key can use, as a URL template the caller fills in client-side with the raw key.
GET Get usage metrics
Returns aggregated request usage for the signed-in account over a time range, broken down by RPC method or by chain.
GET List API keys
Return every API key on the authenticated account, including its public prefix, scopes, and status — but never the raw secret.
DELETE Revoke an API key
Permanently disables one of your API keys so it can no longer authenticate requests.
POST Rotate an API key
Atomically revokes an existing key and issues a replacement that inherits its name, scopes, rate limit, and default flag — returning the new raw secret exactly once.