Base URL
Authentication
Most endpoints require authentication via a Bearer token. See the Authentication guide for full details.Bearer Token
Construct the token by Base64-encodingaccountId:apiKey:
Authorization header:
Response Format
All API responses use a standard envelope:| Field | Type | Description |
|---|---|---|
type | string | Always "response" |
success | boolean | Whether the request succeeded |
description | string | Human-readable description |
data | object | Response payload (empty {} on error) |
error | object | null | Error details, or null on success |
requestId | string | Optional request identifier |
Error Format
Whensuccess is false, the error field contains:
| Field | Type | Description |
|---|---|---|
module | string | Which server module generated the error |
code | string | Machine-readable error code |
message | string | Human-readable error message |
Error Codes
| Code | HTTP Status | Description |
|---|---|---|
UNAUTHORIZED | 401 | Missing or invalid authentication |
FORBIDDEN | 403 | Insufficient permissions |
NOT_FOUND | 404 | Resource not found |
BAD_REQUEST | 400 | Invalid request body or parameters |
CONFLICT | 409 | Resource already exists |
INTERNAL_ERROR | 500 | Server-side error |
VALIDATION_ERROR | 400 | Request body failed validation |
RATE_LIMITED | 429 | Too many requests |
Pagination
List endpoints support pagination withlimit and offset query parameters:
| Parameter | Type | Default | Max | Description |
|---|---|---|---|---|
limit | number | 50 | 100 | Number of results per page |
offset | number | 0 | — | Number of results to skip |
Search & Filtering
Many list endpoints support asearch query parameter for case-insensitive partial matching, and from/to date range filters:
| Parameter | Type | Description |
|---|---|---|
search | string | Case-insensitive partial match on the primary field (name, URL, etc.) |
from | string | ISO date string. Filters created_at >= from |
to | string | ISO date string. Filters created_at <= to |