Authentication
Every request carries a bearer API key in the Authorization header.
Authorization: Bearer $ARADIA_API_TOKENTrying an endpoint without a key
Section titled “Trying an endpoint without a key”Every page in the API Reference carries a console for the endpoint it documents, and each one issues itself a read-only demo token, so you can call the API before signing up for anything. The token is filled in for you and renewed when it expires.
Demo tokens are read-only, expire 15 minutes after they are issued, and are limited to 1 request per second. Issuance itself is capped per IP address. They exist to answer “what does this endpoint return”, not to run against.
You can ask for one directly: see POST /v1/demo-token. Only its hash is stored, so a token cannot be recovered afterwards. Request another instead.
Getting a key
Section titled “Getting a key”Sign in to the Developer Portal with your wallet and create a key. The secret is shown exactly once; store it in your secret manager.
Paste your key into any console and it stops managing the token for you. Clear the field to hand control back.
Scopes
Section titled “Scopes”Keys are issued with read scopes only:
| Scope | Grants |
|---|---|
read:collections |
Collection listings and details |
read:nfts |
Token metadata and collection tokens |
read:owners |
Tokens held by an address |
read:transfers |
Transfer history |
read:activity |
Global activity feed |
read:status |
Indexer status and coverage |
Rotation and revocation
Section titled “Rotation and revocation”Rotate a key to obtain a new secret, or revoke it to reject it immediately. Both actions live in the portal and are recorded in an audit trail.