API overview

The untils API uses RPC-style endpoints over HTTP. Endpoint names are verbs on resources, such as /api/results.list_latest.

Responses are always JSON and structured as:

{
  "data": {}, // result data here, null on error
  "error": {} // error data here, null on success
}

Every resource type includes a type property which can be used to identify the shape of the nested objects without relying on where they appear in the response.

Authorization

API requests use bearer token authorization:

Authorization: Bearer untils.api...

Tokens can be created and revoked from Settings → API tokens. Store tokens as secrets. The full token is only shown once when it is created.

Errors

Errors are returned as JSON with an error object:

{
  "data": null,
  "error": {
    "code": "unauthorized",
    "message": "A valid API token is required."
  }
}

The code value is stable enough for programmatic handling. The message value is intended for logs and debugging, and may change.

Common error codes include:

Reference

• The API reference lists available methods and types.
• The OpenAPI spec contains the machine-readable API definition, which you can use to generate API clients.