Skip to main content

Documentation Index

Fetch the complete documentation index at: https://solvea.cx/docs/llms.txt

Use this file to discover all available pages before exploring further.

API keys let your backend, scripts, or third-party tools call the Solvea OpenAPI on behalf of your workspace. Each key is bound to the workspace that created it, so every request is automatically scoped — no extra tenant header required.
An API key carries the same access as your workspace. Treat it like a password — never commit it to a public repository, paste it into a chat, or ship it in client-side code.

​
Generate an API key

  1. Open the Solvea dashboard at app.solvea.cx.
  2. In the sidebar, go to API Keys.
    API Keys entry in the sidebar
  3. Click Generate API Key.
    Generate API Key button
  4. Confirm in the dialog that appears.
    Create API key confirmation dialog
  5. Click the copy button on the right of the key to copy it to your clipboard, then use it in your application.
    Newly created API key with copy button
Each workspace can have only one API key at a time. To issue a new key, delete the existing one first (see Rotate or delete a key).

​
Key format

A Solvea API key starts with the sk- prefix followed by a random hex string. The sk- prefix makes the key easy to spot in logs and lets secret-scanning tools (GitHub, gitleaks, etc.) catch accidental commits.

​
Use the API key

Every OpenAPI request needs a single header:
HeaderValuePurpose
AuthorizationBearer sk-…Authenticates the calling application and identifies your workspace

​
Base URL

The Solvea OpenAPI is served from https://app.solvea.cx. All endpoints live under the /api_v2/... path prefix.

​
Example request

A quick way to verify your key works is to list the phone numbers available to your workspace: 
curl https://app.solvea.cx/api_v2/gpt/api/voice/phone-number/business/available \
  -H "Authorization: Bearer $SOLVEA_API_KEY"
Node.js
const res = await fetch(
  "https://app.solvea.cx/api_v2/gpt/api/voice/phone-number/business/available",
  {
    headers: {
      Authorization: `Bearer ${process.env.SOLVEA_API_KEY}`,
    },
  },
);
Python
import os, requests

requests.get(
    "https://app.solvea.cx/api_v2/gpt/api/voice/phone-number/business/available",
    headers={
        "Authorization": f"Bearer {os.environ['SOLVEA_API_KEY']}",
    },
)
A 200 response with a JSON body confirms the key is wired up correctly.

​
Rotate or delete a key

To rotate a key (for example, after a suspected leak or when an employee leaves):
  1. Go to API Keys in the dashboard.
  2. Click the delete (trash) icon next to your existing key and confirm.
  3. Click Generate API Key to create a new one, and update the secret in every system that uses it.
Deletion takes effect immediately. Any service still using the old key will start receiving 401 Unauthorized as soon as the key is removed, so update your secrets first or schedule a brief maintenance window.

​
Error reference

Common responses you may see from the OpenAPI:
HTTPMeaningWhat to check
401Missing or invalid Authorization header, or the key has been deleted/disabledVerify the Bearer sk-… value matches the key shown in the dashboard. Generate a new one if needed.
403The key is valid but the workspace isn’t allowed to access this resourceCheck the resource belongs to the workspace that owns this key.
422The request was authenticated but failed validationRead the response message field for the specific reason.

​
Security checklist

  • Store keys in a secret manager, never in source control.
  • Use a separate key per integration or environment.
  • Rotate keys on a regular cadence and immediately if a leak is suspected.
  • Restrict access to the API Keys page to people who need it.
  • Watch your logs for the sk- prefix to catch accidental exposure.