Skip to main content
The Gliiv API uses API keys to authenticate requests. This ensures that every message sent programmatically is authorized and linked to your specific account.

​
Obtaining your API Key

To get started, generate a unique key from your account dashboard. You can create up to 3 API keys per account.
  1. Navigate to the API Settings page.
  2. Click the Create Key button to open the configuration modal.
  3. Configure your key settings (optional):
    • Name: Give your key a descriptive label (defaults to "API Key" if left blank).
    • Expires at: Select an expiration date and time (defaults to Never / Valid forever if left blank).
  4. Click submit, then copy and save your generated key immediately.
Important: API keys are displayed only once at the time of creation. For security reasons, Gliiv does not store unencrypted keys and cannot retrieve them after you leave or refresh the page. If a key is lost or compromised, you must delete it and generate a new one.

​
Header Authentication

All API requests must include the x-api-key header. Requests that omit this header or provide an invalid key will be rejected with a 401 Unauthorized response.

​
Header Specification

​
string
required
Your secret API key (formatted as gliiv_xxxxxxxxxxxxxxxx).

​
Example Header

Your request headers should be structured as follows:

​
Security Best Practices

  • Server-Side Only: Never expose your x-api-key in client-side code, frontend JavaScript, or public repositories.
  • Storage: Store your key securely using environment variables or a secrets management service.
  • Replacement: If you suspect your key has been compromised, revoke it immediately in the dashboard and generate a replacement.
Last modified on September 13, 2026