pdx_ and shown once at creation; the full value is hashed on the server immediately and cannot be retrieved again. These endpoints require a console session JWT.
Authentication
All key management endpoints require a session JWT from the Developer Console auth flow:Endpoints
| Method | Path | Description |
|---|---|---|
POST | /api/v1/console/keys | Create a new API key |
GET | /api/v1/console/keys | List your API keys |
DELETE | /api/v1/console/keys/{id} | Revoke a key permanently |
Create an API key
Request body
Human-readable label for the key, e.g.
"Production Trading Bot". 1–100 characters.JSON-encoded array of permission strings. Default grants read access to arbitrage, markets, and questions.
Custom rate limit in requests per minute. Range 1–10,000. Defaults to 60.
Example request
cURL
CreateAPIKeyResponse fields
API key UUID. Use this to revoke the key later.
The label you assigned.
The full API key, prefixed with
pdx_. This is the only time the full key is returned. Store it in a secrets manager immediately.First 12 characters of the key, used for identification in future list responses, e.g.
pdx_a1b2c3d4.JSON-encoded permissions array as stored.
Rate limit in requests per minute.
Warning message confirming the key will not be shown again.
Sample response
List API keys
Example request
cURL
APIKeyInfo fields
API key UUID.
Human-readable label.
First 12 characters for identification, e.g.
pdx_a1b2c3d4.JSON-encoded permission array.
Rate limit in requests per minute.
false if the key has been revoked.ISO 8601 timestamp of the most recent successful request.
null if the key has never been used.ISO 8601 timestamp when the key was created.
Sample response
Revoke an API key
401 INVALID_API_KEY. Revocation is permanent — the key cannot be reactivated.
Path parameters
UUID of the API key to revoke.
Example request
cURL
