API Overview
The Revor AI API supports connected account lookup, outreach task creation, LinkedIn post engagement, and task result retrieval.
Base URL
https://revor.ai/api/v1
Authentication
Every request must include an API key. The recommended authentication method is the Authorization: Bearer header.
cURLcurl "https://revor.ai/api/v1/connect/accounts" \ -H "Authorization: Bearer sk-revor-REPLACE_ME"
The x-api-key header is also supported.
cURLcurl "https://revor.ai/api/v1/connect/accounts" \ -H "x-api-key: sk-revor-REPLACE_ME"
Response Format
Successful responses include ok: true and request_id. List endpoints return items; single-resource and task endpoints return item.
JSON{ "ok": true, "request_id": "req_xxx", "item": {} }
Error responses include ok: false and error. Keep request_id when reporting an issue.
JSON{ "ok": false, "error": { "code": "api_key_invalid", "message": "api_key_invalid", "request_id": "req_xxx" } }
Idempotency
Endpoints support Idempotency-Key. For the same API key, path, and Idempotency-Key:
- Same request body: Revor AI returns the original response and does not create another task.
- Different request body: Revor AI returns
409 idempotency_conflict.
Use Idempotency-Key for network timeouts, interrupted connections, or client retries. Each new outreach action should use a new Idempotency-Key.
Asynchronous Tasks
Outreach creation and LinkedIn post-like requests return HTTP 202 Accepted. The response item.id is the task ID. Use GET /api/v1/outreach/jobs/{id} to retrieve the final result.
Rate Limits
If requests are sent too frequently, Revor AI returns 429 api_rate_limit_exceeded. Responses may include these headers:
Endpoints
Recommended Flow
- Call
GET /api/v1/connect/accountsto list available accounts. - Use the returned
account_idto create an outreach task or a LinkedIn post-like task. - Read
item.idfrom the creation response. - Call
GET /api/v1/outreach/jobs/{id}to retrieve the task result.