API reference — Klerix

Authentication

Every request must include an Authorization: Bearer header. Tokens are scoped to a workspace and rotateable from the dashboard.

curl https://api.klerix.com/v1/runs \
  -H "Authorization: Bearer $KLERIX_TOKEN"

Trigger a workflow run

POST /v1/workflows/:id/runs

{
  "input": { "claim_id": "CL-9182" },
  "idempotency_key": "resubmit-CL-9182"
}

Returns a run_id. Poll /v1/runs/:run_id or subscribe via webhook.

List workflows

GET /v1/workflows?limit=25&cursor="..."

Webhooks

Events: run.started, run.step, run.needs_review, run.succeeded, run.failed. Signed with X-Klerix-Signature.

{
  "event": "run.succeeded",
  "run_id": "r_84221",
  "workflow": "claims-resubmit",
  "output": { "accepted": true }
}

MCP server

Klerix exposes an MCP server so that LLM agents (Claude, GPT-5) can compose Klerix workflows as tools. Point your MCP-compatible client at mcp.klerix.com.

Errors