Getting Your API Key

​

Step 1: Open the Console

​

Step 2: Generate the Key

You hold one active API key at a time. Generating a new key revokes the previous one immediately, so any service still sending the old value starts receiving 403. There is no overlap window: roll the new key out as soon as you generate it.

Keep it secret. The key carries your account’s permissions. Store it in an environment variable, never commit it, and never ship it in client-side code.

​

Step 3: Use the API Key in Requests

Authorization: Bearer <your_api_key>

const response = await fetch(`https://api.defindex.io/vault/${vaultAddress}/deposit`, {
    method: 'POST',
    headers: {
        'Content-Type': 'application/json',
        'Authorization': `Bearer ${process.env.DEFINDEX_API_KEY}`
    },
    body: JSON.stringify(params)
});

​

Key Lifetime and Rotation

• You generate a new key, which revokes the previous one.
• You revoke it explicitly from the API Keys section of the console.

refresh_token is unrelated to your API key. /login and /refresh issue short-lived JWT access tokens, which is how the console authenticates its own session. If you authenticate with an API key, you never call /refresh.

​

Next Steps

• Getting Started with the API
• Beginner Guide — Vault Deposit Example
• Full API Reference

​

Need Help?