Question 1

How do I create an API key?

Accepted Answer

1. Sign in to the developer console 2. Select the target organization and project 3. Open API keys and click Create API key 4. Name the key (e.g. `prod-backend`) 5. Copy and store the full secret immediately Keys look like `sk-snx-...`. Send `Authorization: Bearer <YOUR_KEY>` on each request. Related: Authentication · Console API keys

Question 2

Why is the full secret shown only once?

Accepted Answer

For security, SupaNexus stores only a hash of the key. The plaintext cannot be shown again. If you lose it, revoke the old key and create a new one. Store new keys in a secrets manager or environment variables — never in source control.

Question 3

What happens when a key is revoked or expires?

Accepted Answer

Requests return 401 with `invalid_api_key`. The call is not billed. Check: revocation status, expiry, and `Bearer <key>` header formatting. Related: Authentication · Errors

Question 4

How should I separate production and test environments?

Accepted Answer

Recommended: - Separate projects for dev / beta / prod - Separate keys per environment for usage visibility and per-key spend caps - Separate env vars in CI/CD and runtime — never mix keys Do not use production keys in test environments or log full secrets.

API Keys