RevorRevor

Find more prospects

POST/api/v2/websets/{webset_id}/find-more

Starts another discovery run on an existing Webset. count is the desired number of additional prospects, not a new total. Requires websets:write, consumes credits, and runs asynchronously.

Before calling

Read the current Items snapshot and retain the first page's stream_cursor + items_revision. After Find More is accepted, this old checkpoint lets the stream replay every change from the new run.

Request

Idempotency-Key is required. Reuse it when retrying the same operation after a network failure.

cURL
curl -X POST "https://revor.ai/api/v2/websets/WEBSET_ID/find-more" \
  -H "Authorization: Bearer sk-revor-REPLACE_ME" \
  -H "Idempotency-Key: find-more-001" \
  -H "Content-Type: application/json" \
  -d '{"count":25}'

count may be 25, 100, 500, or 1000 and is limited by the current plan.

Response

HTTP 202:

JSON
{
  "ok": true,
  "request_id": "req_xxx",
  "item": {
    "id": "job-uuid",
    "action": "websets.find_more",
    "status": "queued",
    "progress": {
      "stage": "queued",
      "percent": 0
    },
    "resource": {
      "type": "webset",
      "id": "webset-uuid"
    },
    "scheduled_at": "2026-09-24T08:10:00.000Z",
    "started_at": null,
    "finished_at": null,
    "attempt_count": 0,
    "result": null,
    "error": null,
    "billing": {
      "status": "pending",
      "charged_credits": 0,
      "pending_units": 0
    }
  }
}

Save item.id as the job_id, then open Find More SSE. A missing key returns 400 idempotency_key_required. Reusing one key for another request returns 409 idempotency_conflict.