API Reference

LaserData Cloud provides a main API and regional Supervisor APIs. Programmatic requests use an ld-api-key header with a key whose role permits the operation.

These APIs manage resources, configuration, and monitoring. For application messages, queries, and agents, use laser-sdk in Rust, Python, or TypeScript.

Base URLs

List Deployments and Get Deployment return each deployment's supervisor_url. An example is https://supervisor-aws-us.laserdata.cloud.

OpenAPI Schema

Each public service provides an OpenAPI 3.1 specification and browser, with request and response examples.

Agents and generators can start at https://laserdata.com/openapi.json, the Core management API specification. Individual service specifications are also available:

Each operation has a stable, unique operationId, description, typed parameters, and typed responses. For an LLM function tool, use operationId as its name. Use the description as guidance and request parameters or body schema as inputs. Send credentials only to the declared LaserData service base URL.

Main, Audit, Notifier

Open api.laserdata.cloud/docs and use the dropdown to select Core, Audit, or Notifier.

Supervisor (per region)

Each cloud and area has a supervisor specification at /docs:

Specifications declare ld_api_key and session_cookie. User-session endpoints explicitly require cookies and reject API keys. See Authentication.

Authentication

For API-key authentication, include ld-api-key:

curl https://api.laserdata.cloud/tenants/{tenant_id}/api_keys \
-H "ld-api-key: YOUR_API_KEY"

Authentication explains scopes, security, and error responses.

Pagination

List endpoints accept these pagination parameters:

Paginated bodies include items, page, total_results, and total_pages. The RFC 8288 Link header provides rel="first", prev, next, and last URLs. Clients can follow those links without parsing pagination fields.

Request and Response Headers

Idempotency

POST, PUT, and PATCH accept optional idempotency-key for safe retries. The platform caches the first response for each (api_key, idempotency-key) pair for 10 minutes. Repeating the same body with the same key returns that response with idempotent-replayed: true. The handler does not run again.

• This feature applies to API-key authentication. Console sessions do not use it.
• A repeated key with a different body returns 409 Conflict and code: idempotency_error.
• A retry while the original request runs returns 409 Conflict and code: idempotent_request_in_progress. Wait briefly before retrying.
• DELETE is excluded because repeated deletion already has the same effect.
• Audit has no endpoints that change state and does not advertise idempotency support.

Use the same request identity after network failures, CI retries, or queue redelivery, including when creating deployments.

Quick Start

Create a Free single-node deployment, then retrieve its details and credentials:

# 1. Create a starter deployment (Free, single node on shared infrastructure)
curl -X POST https://api.laserdata.cloud/tenants/{tenant_id}/divisions/{division_id}/deployments/starter \
-H "ld-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "cloud": "aws",
  "region": "us-west-1"
}'

# Response headers contain the created resource IDs:
# ld-environment: <environment_id>
# ld-deployment: <deployment_id>

# 2. Get the deployment (once provisioned)
curl https://api.laserdata.cloud/tenants/{tenant_id}/divisions/{division_id}/environments/{environment_id}/deployments/{deployment_id} \
-H "ld-api-key: YOUR_API_KEY"

# 3. Get connection credentials
curl {supervisor_url}/deployments/{deployment_id}/credentials \
-H "ld-api-key: YOUR_API_KEY"

HTTP Status Codes

API Sections