RevorRevor

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.

cURL
curl "https://revor.ai/api/v1/connect/accounts" \
  -H "Authorization: Bearer sk-revor-REPLACE_ME"

The x-api-key header is also supported.

cURL
curl "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:

HeaderDescription
X-RateLimit-LimitAPI key limit for the current window.
X-RateLimit-RemainingRemaining API key requests in the current window.
X-RateLimit-Window-MsAPI key window length in milliseconds.
X-User-RateLimit-LimitAccount limit for the current window.
X-User-RateLimit-RemainingRemaining account requests in the current window.
Retry-AfterSuggested wait time in seconds.

Endpoints

EndpointMethodDescriptionReference
/api/v1/connect/accountsGETList Connect accounts available for outreach.List Connect Accounts
/api/v1/outreach/dispatchesPOSTCreate an email, LinkedIn, or WhatsApp outreach task.Create Outreach Dispatch
/api/v1/outreach/linkedin/post-likesPOSTLike one relevant post from a target LinkedIn profile.Like LinkedIn Post
/api/v1/outreach/jobs/{id}GETRetrieve outreach task status and result.Check Outreach Job
  1. Call GET /api/v1/connect/accounts to list available accounts.
  2. Use the returned account_id to create an outreach task or a LinkedIn post-like task.
  3. Read item.id from the creation response.
  4. Call GET /api/v1/outreach/jobs/{id} to retrieve the task result.

Common Errors

HTTPCodeDescription
400invalid_requestThe request parameters are invalid.
401api_key_missingNo API key was provided.
401api_key_invalidThe API key is invalid.
401api_key_expiredThe API key has expired.
401api_key_revokedThe API key has been revoked.
403permission_deniedThe API key does not have access to the endpoint or resource.
409idempotency_conflictThe idempotency key was reused with a different request body.
429api_rate_limit_exceededThe request was rate limited.
503task_unavailableThe task could not be created temporarily.