API Conventions - Zevari Docs
Errors, rate limits, pagination, idempotency, and verbs for the Zevari REST API.
Errors
Every error uses a stable envelope: { error: { code, message, docs_url, suggested_action } }. code is a stable string you can switch on; message is human-readable; docs_url links the relevant docs; suggested_action hints the fix.
Rate limits
600 requests per key per hour. Over the limit, the API returns HTTP 429 with error code rate_limited. There are no Retry-After or X-RateLimit headers, so back off on a fixed schedule and retry.
Pagination
Entity list endpoints use offset and limit. LinkedIn search endpoints return an opaque cursor; pass it back to get the next page.
Idempotency
Idempotency keys are not supported. For approval-gated writes, the safe retry is re-calling with the same confirmation_id.
Verbs
GET for reads, PATCH for updates, DELETE for deletes, POST for actions and creates.