Skip to main content
API keys give automated clients — trading bots, data pipelines, and server-side integrations — access to Predexy’s external endpoints without a browser session. Each key is prefixed with 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


Create an API key

Generates a new API key for your account. The response includes the full raw key — copy it now because it will not be shown again.

Request body

string
required
Human-readable label for the key, e.g. "Production Trading Bot". 1–100 characters.
string
JSON-encoded array of permission strings. Default grants read access to arbitrage, markets, and questions.
number
default:"60"
Custom rate limit in requests per minute. Range 1–10,000. Defaults to 60.

Example request

cURL

CreateAPIKeyResponse fields

string
required
API key UUID. Use this to revoke the key later.
string
required
The label you assigned.
string
required
The full API key, prefixed with pdx_. This is the only time the full key is returned. Store it in a secrets manager immediately.
string
required
First 12 characters of the key, used for identification in future list responses, e.g. pdx_a1b2c3d4.
string
required
JSON-encoded permissions array as stored.
number
required
Rate limit in requests per minute.
string
required
Warning message confirming the key will not be shown again.

Sample response

Copy the key field from the response immediately. The server stores only a hash of the key — there is no way to recover or display the full value after this response is received. If you lose the key, revoke it and create a new one.

List API keys

Returns all API keys for your account. Only the key prefix is shown — the full key is never returned after creation.

Example request

cURL

APIKeyInfo fields

string
required
API key UUID.
string
required
Human-readable label.
string
required
First 12 characters for identification, e.g. pdx_a1b2c3d4.
string
required
JSON-encoded permission array.
number
required
Rate limit in requests per minute.
boolean
required
false if the key has been revoked.
string
ISO 8601 timestamp of the most recent successful request. null if the key has never been used.
string
required
ISO 8601 timestamp when the key was created.

Sample response


Revoke an API key

Deactivates the key immediately. Any in-flight request using the revoked key will receive 401 INVALID_API_KEY. Revocation is permanent — the key cannot be reactivated.

Path parameters

string
required
UUID of the API key to revoke.

Example request

cURL

Sample response