Skip to main content
Kelviq API uses API keys to authenticate requests. All API requests must be made over HTTPS; calls made over plain HTTP will fail. API requests without authentication will also fail.

​
API Keys

Kelviq provides two types of API keys for different use cases.

Client API Key

Used for frontend applications where the key is publicly accessible.

Server API Key

Used for backend implementations. This key has more privileges and must be kept secret.
Environment Scoping: API keys are scoped per environment. This means your production and sandbox environments will have separate and distinct API keys.
Learn how the sandbox works →
Important Security Notice: Do not share your Server API Key in any publicly accessible areas such as frontend code, client-side applications, or public repositories.

​
Obtaining Your API Key

You can get your API key from the Kelviq application dashboard.
  1. Navigate to Settings.
  2. Go to the API keys section.
  3. Copy the key appropriate for your integration:
    • Client API Key for supported calls made from browsers or distributed applications.
    • Server API Key for calls made from your trusted backend.

​
Authorization

To authenticate your requests, pass the appropriate API key as a Bearer token in the Authorization header.
Most management APIs require a Server API Key. The License Activate, Validate, and Deactivate APIs accept either a Client API Key or a Server API Key, allowing license lifecycle calls from both customer-facing software and trusted backends. Check each endpoint’s authentication note before using a Client API Key. Learn about license API authentication →