Environments & Deployment
How KLIQ runs, and how to point the SDK at the right environment.
Environments
KLIQ provides three environments. Each has its own base URL and key prefix so you can never accidentally hit production from a test run.
| Environment | Base URL | Key prefix | Purpose |
|---|---|---|---|
| Production | https://api.kliq-ai.eu | kliq_sk_ | Live tenant data and workloads |
| Staging | https://staging-api.kliq-ai.eu | kliq_sk_ | Pre-release verification (internal) |
| Sandbox | https://sandbox-api.kliq-ai.eu | kliq_test_ | Isolated trial environment (see Sandbox) |
Keys are not interchangeable
A kliq_test_ key only works against sandbox-api.kliq-ai.eu. A kliq_sk_ key only works against production or staging. Sending a sandbox key to the production endpoint — or a live key to the sandbox — will return a 401 Unauthorized error.
Selecting an environment from the SDK
By default, KliqClient targets production. Pass baseUrl to override:
import { KliqClient } from '@kliq-ai/sdk';
// Production (default)
const kliq = new KliqClient({ apiKey: process.env.KLIQ_API_KEY! });
// Sandbox — use your kliq_test_ key
const sandbox = new KliqClient({
apiKey: process.env.KLIQ_TEST_API_KEY!,
baseUrl: 'https://sandbox-api.kliq-ai.eu',
});
A shorthand environment option is planned for Part B of the SDK — when it ships you will be able to write environment: 'test' instead of supplying the full baseUrl. Until then, use the explicit baseUrl form shown above.
How releases reach you
When a change merges to main, it is automatically deployed to the staging environment where it goes through pre-release verification. Once staging is confirmed healthy, an engineer triggers a manual, approval-gated promotion to production. This means every change that reaches https://api.kliq-ai.eu has already been exercised in staging first, and no deployment reaches production without explicit sign-off.