Skip to main content

Endpoint

The API is REST over HTTPS. Plain HTTP isn’t accepted.

Authentication

Send your API key as a Bearer token on every request:

API key

Create an API key

1

Go to your workspace

Open Profile > API Keys in your workspace.
2

Create the key

Click Create and pick the scopes this key should carry.
3

Use it

Send the key as a Bearer token on every request:

Scopes

A key carries scopes that limit what it can do. Select only the scopes the integration needs to reduce the impact of an exposed key.

Errors

Every error response is JSON with the same shape. error is human-readable. requestId correlates with the X-Lora-Request-Id response header; quote it when filing a support ticket. traceId is a trace identifier when one is available. code is optional, and when present it’s a machine-readable handle you can branch on. Minimum shape:
With a machine-readable code:

What a 401 means

Missing, malformed, unknown, and expired keys return the same generic 401 body:
There’s no code field on the generic 401. A disabled key returns the same status with code: "apikey_disabled". Treat any 401 as “your request wasn’t authenticated” and check the key you sent. If the key is valid but lacks the scope an endpoint needs, you get 403 with code: "insufficient_scope" and a required_scope field naming what was missing.

Common error codes

The endpoint reference documents the responses for each operation. These are the shared and frequently returned machine-readable codes. New codes may be added.

Retry safety

Retry idempotent operations with exponential backoff. A write that returns 500 may already have applied. Read the resource or otherwise reconcile its state before retrying the write.