API
Authentication
How to authenticate requests to the Dex API.
To call Dex API endpoints, include your API key as a Bearer token.
Base URL
https://api.prod.getdex.com
Required header
Authorization: Bearer dex_your_api_key
Content-Type: application/json
Keep your API key private. Never expose it in client-side apps, public repos, or screenshots.
Create an API key
- Open Settings → Workflow → Dex API & MCP.
- Click Create API key, give the key a name, choose its access, and click Create key.
- Copy the key from the dialog, including its
dex_prefix, and store it somewhere safe.
A full key is dex_ followed by 64 characters. If Dex rejects a key you just created, check that the whole key was copied.
Dex shows a key in full only once, in the dialog right after you create or regenerate it. After that, the Settings list shows a masked key such as
dex_••••••••a1b2, so you can tell keys apart but can't copy them again. If you lose a key, regenerate it or create a new one.Dex Professional required. Creating a personal key, regenerating it and calling the API with it all need the Dex Professional plan.
Regenerating replaces your key. Open the key's menu in the list and choose Regenerate. The existing key stops working immediately, so any integration using it, including Zapier, has to be updated with the new one.
Rate limits
Each account can make 100 requests per minute. The limit is shared across all of your keys and resets every minute.
Going over it returns HTTP 429 with the error code rate_limited. The connection isn't dropped. Wait for the number of seconds in the Retry-After header, then retry. Every response also carries x-ratelimit-remaining and x-ratelimit-reset headers, so you can slow down before you hit the limit.
Quick test
curl --request GET \
--url https://api.prod.getdex.com/v1 \
--header 'Authorization: Bearer dex_your_api_key'