Conventions

Pagination

Every list endpoint is cursor-paginated. Pass a limit (default 50, maximum 200); the response carries the page of results plus a next_cursor. Pass that cursor back to fetch the next page. When next_cursor is null, you have reached the end.

curl -H "Authorization: Bearer jmt_..." \
  "https://rigyx.com/api/public/v1/leads?limit=50&cursor=5b2e...-uuid"

{
  "data": [
    { "id": "...", "email": "[email protected]", "status": "new" }
  ],
  "next_cursor": "a1b2...-uuid"
}

Idempotency

Any POST can carry an Idempotency-Key header — a unique string you choose. The first request runs normally; for 24 hours any repeat with the same key returns the original response instead of running again. Keys are scoped to (business, key, method, path).

This makes retries safe — a network timeout on a POST /leads can be retried with the same key without creating the lead twice.

curl -X POST https://rigyx.com/api/public/v1/leads \
  -H "Authorization: Bearer jmt_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: import-2026-05-22-row-001" \
  -d '{"email": "[email protected]", "company_name": "Acme"}'

Rate limits

Each token gets 60 requests per minute by default, measured over a sliding 60-second window. Every response carries your current budget:

X-RateLimit-Limit: 60
X-RateLimit-Remaining: 57

Exceed the limit and the request returns 429 with a Retry-After header telling you how many seconds to wait:

Retry-After: 12

{
  "error": "Rate limit exceeded (60 req/min). Retry after 12s.",
  "code": "RATE_LIMIT_EXCEEDED",
  "retry_after": 12
}

Errors

Every error — on any endpoint — uses the same JSON shape. A human-readable error, a stable machine-readable code, and an optional details object. Branch your code on code, never on the message text.

{
  "error": "This token is missing the required scope: leads:write",
  "code": "INSUFFICIENT_SCOPE",
  "details": { "required_scope": "leads:write" }
}