Your privacy choices

We use essential storage to operate Lexel Translate. With your permission, we also use analytics, advertising, and marketing technologies. Read our Cookie Policy.

API keys

Create, rotate, inspect, update, and revoke managed API keys for personal, organization, and team scopes. Session auth only.

Access and visibility

API keys are bearer credentials: anyone holding the secret can make translation requests without signing in. Personal keys spend personal Premium characters. Organization and team keys spend organization Premium characters; team keys attribute usage to that team. Keep all keys private and revoke exposed keys.

Personal keys are visible only to their owner. Organization owners and admins can list and manage organization and team keys created by any admin. Ordinary organization members and team leads do not gain key-management access through membership alone. Existing secrets cannot be retrieved; they are shown only when created or rotated.

Endpoints

GET/api/v1/api-keys

List accessible API keys.

POST/api/v1/api-keys

Create a new managed API key.

GET/api/v1/api-keys/:apiKeyId

Read one API key.

PATCH/api/v1/api-keys/:apiKeyId

Update mutable key fields.

POST/api/v1/api-keys/:apiKeyId/rotate

Rotate a key and return the new raw key once.

DELETE/api/v1/api-keys/:apiKeyId

Revoke a key.

Create request

curl -X POST "https://translate.lexel.ai/api/v1/api-keys" \
  -H "Cookie: better-auth.session_token=your_session_cookie" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "Production translation key",
  "target": "organization",
  "organizationId": "org_123"
}'

Create fields

Field	Type	Required	Description
name	string \| null	No	Display name for the key.
target	user \| organization \| team	Yes	Ownership scope for the new API key.
organizationId	string \| null	No	Required when target is organization.
teamId	string \| null	No	Required when target is team.

Update fields

Field	Type	Required	Description
name	string	No	Updated display name.
enabled	boolean	No	Enable or disable the key.
historyTrackingEnabled	boolean	No	History control for the key scope.

Create response example

json

{
  "ok": true,
  "apiKey": {
    "id": "key_123",
    "name": "Production translation key",
    "organizationId": "org_123",
    "teamId": null,
    "enabled": true
  },
  "rawKey": "lxl_your_new_secret_key"
}

Rotate example

curl -X POST "https://translate.lexel.ai/api/v1/api-keys/key_123/rotate" \
  -H "Cookie: better-auth.session_token=your_session_cookie"

json

{
  "ok": true,
  "apiKey": {
    "id": "key_123",
    "name": "Production translation key",
    "organizationId": "org_123",
    "teamId": null,
    "enabled": true
  },
  "rawKey": "lxl_rotated_secret_key"
}

Next steps

The raw key is only returned on create and rotate. Store it immediately.
Public translation callers use the generated bearer key against /api/v1/translate and related execution routes. They do not manage key lifecycle through API key auth.

API keys

Create, rotate, inspect, update, and revoke managed API keys for personal, organization, and team scopes. Session auth only.

Access and visibility

Endpoints

GET/api/v1/api-keys

List accessible API keys.

POST/api/v1/api-keys

Create a new managed API key.

GET/api/v1/api-keys/:apiKeyId

Read one API key.

PATCH/api/v1/api-keys/:apiKeyId

Update mutable key fields.

POST/api/v1/api-keys/:apiKeyId/rotate

Rotate a key and return the new raw key once.

DELETE/api/v1/api-keys/:apiKeyId

Revoke a key.

Create request

curl -X POST "https://translate.lexel.ai/api/v1/api-keys" \
  -H "Cookie: better-auth.session_token=your_session_cookie" \
  -H "Content-Type: application/json" \
  -d '{
  "name": "Production translation key",
  "target": "organization",
  "organizationId": "org_123"
}'

Create fields

Field	Type	Required	Description
name	string \| null	No	Display name for the key.
target	user \| organization \| team	Yes	Ownership scope for the new API key.
organizationId	string \| null	No	Required when target is organization.
teamId	string \| null	No	Required when target is team.

Update fields

Field	Type	Required	Description
name	string	No	Updated display name.
enabled	boolean	No	Enable or disable the key.
historyTrackingEnabled	boolean	No	History control for the key scope.

Create response example

json

{
  "ok": true,
  "apiKey": {
    "id": "key_123",
    "name": "Production translation key",
    "organizationId": "org_123",
    "teamId": null,
    "enabled": true
  },
  "rawKey": "lxl_your_new_secret_key"
}

Rotate example

curl -X POST "https://translate.lexel.ai/api/v1/api-keys/key_123/rotate" \
  -H "Cookie: better-auth.session_token=your_session_cookie"

json

{
  "ok": true,
  "apiKey": {
    "id": "key_123",
    "name": "Production translation key",
    "organizationId": "org_123",
    "teamId": null,
    "enabled": true
  },
  "rawKey": "lxl_rotated_secret_key"
}

Next steps

The raw key is only returned on create and rotate. Store it immediately.
Public translation callers use the generated bearer key against /api/v1/translate and related execution routes. They do not manage key lifecycle through API key auth.