API Reference

Wacht exposes two distinct HTTP APIs with different purposes, audiences, and authentication models. Understanding which one to use is the first step.

Choosing the right API

Response format

Both APIs return JSON. Successful responses wrap the payload in a data envelope:

{
  "data": { ... }
}

List endpoints return paginated results with cursor metadata:

{
  "data": [...],
  "has_more": true,
  "limit": 20,
  "offset": "cursor_token"
}

Errors follow a consistent shape across both APIs:

{
  "error": {
    "code": "resource_not_found",
    "message": "The requested resource could not be found.",
    "status": 404
  }
}

SDKs

For most use cases you should use an SDK rather than calling the APIs directly. The SDKs handle authentication, session management, and type safety automatically.