Registration and API Keys

API requests use Bearer token authentication. A key represents your account's permissions; protect it like a password.

Create a keyCopy Anchor Link

1. Register and sign in. Create an account on the APIQIK website and complete the required account verification.
2. Open the console. Go to token management and choose to create a new key.
3. Name and save the key. Use a name that identifies its environment or application, such as prod-chat-service, and save the full key immediately.
4. Plan budgets and monitoring. Before production, check your balance, how to view usage, and your internal alert thresholds.

Save the key immediately if it is only shown once. Never paste a real key into documentation, support tickets, public screenshots, or frontend code. Support does not need your complete API key.

Set environment variablesCopy Anchor Link

macOS / LinuxCopy Anchor Link

export APIQIK_API_KEY="YOUR_API_KEY"

Windows PowerShellCopy Anchor Link

$env:APIQIK_API_KEY = "YOUR_API_KEY"

Request headersCopy Anchor Link

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Production security checklistCopy Anchor Link

• Store keys only in server-side environment variables or a dedicated secrets manager.
• Use different keys for development, testing, and production to separate permissions and billing.
• Rotate keys regularly. If a key leaks, revoke it immediately and create a replacement.
• Log only a key fingerprint or a few trailing characters, never the complete value.
• Browser and mobile clients should call APIQIK through your backend rather than embedding keys directly.