API

Authentication

Make a key in the workspace’s Settings → API keys; it is shown once. Send it with every request:

curl https://api.reachpool.ai/v1/campaigns \
  -H "Authorization: Bearer rp_live_…"

• A key works in its workspace only, as the person who made it, with their role there.
• It stops working when it is revoked, or when that person leaves the workspace: then every call answers 401.
• The workspace’s id, for workspaceId, is shown beside its keys in Settings.

Limits

600 requests a minute per key. Every answer carries X-RateLimit-Limit and X-RateLimit-Remaining; over the limit, 429 rate_limited with Retry-After in seconds.

Answers and errors

Answers are JSON under data. Lists come a page at a time: pass the meta.nextCursor you got as ?cursor= for the next page, until it is null. Errors look like this:

{ "error": { "code": "validation_error", "message": "request failed validation",
             "issues": [{ "path": "profileUrl", "message": "Required" }] } }

Adding leads from other tools

POST /v1/leads takes one lead, or up to 500 under leads. Only profileUrl is required; a lead already in the workspace is updated, not added twice, and an excluded one is left out.

curl -X POST https://api.reachpool.ai/v1/leads \
  -H "Authorization: Bearer rp_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "workspaceId": "…", "profileUrl": "https://www.linkedin.com/in/ada-lovelace/",
        "firstName": "Ada", "company": "Analytical Engines" }'

The answer counts what happened: created, deduped, excluded and invalid, with each row’s lead id in ids. Attach them to a campaign with POST /v1/campaigns/{id}/leads.

Zapier

1. Add an action step: Webhooks by Zapier → POST.
2. URL https://api.reachpool.ai/v1/leads, Payload Type Json.
3. Data: workspaceId, profileUrl and any of firstName, lastName, company, title, email, mapped from the trigger.
4. Headers: Authorization = Bearer rp_live_….

Make

1. Add HTTP → Make a request: URL https://api.reachpool.ai/v1/leads, Method POST.
2. Headers: Authorization = Bearer rp_live_….
3. Body type Raw, Content type JSON (application/json), Request content: the JSON above, with values mapped from earlier modules.

Webhooks

Add a webhook in the workspace’s Settings → Webhooks (or with POST /v1/webhooks): an https URL and the events it takes. Each event is POSTed as JSON:

{ "id": "4f0c…",            // the event's id: the same on every retry
  "type": "lead.replied",
  "createdAt": "2026-11-02T09:14:03.120Z",
  "workspaceId": "…",
  "data": { "senderId": "…", "leadId": "…", "campaignId": "…", … } }

• data holds ids and states, never the words of a message; fetch the rest with the API, e.g. GET /v1/conversations/{id}.
• Answer with any 2xx within 10 seconds. Anything else, a redirect or no answer is tried again after 1 minute, 10 minutes, 1 hour, 6 hours and 24 hours, then marked failed: it can be sent again from the webhook’s page.
• An event can arrive more than once (when your answer was lost): skip an id you have seen.
• Send test event on the webhook’s page sends webhook.test.

Checking the signature

Every request carries X-Signature: sha256=…, the HMAC-SHA256 of the raw body with the webhook’s secret (shown once, when it was made). Compare it before trusting the body:

import { createHmac, timingSafeEqual } from 'node:crypto';

function signed(rawBody, header, secret) {
  const expected = 'sha256=' + createHmac('sha256', secret).update(rawBody).digest('hex');
  return header?.length === expected.length &&
    timingSafeEqual(Buffer.from(header), Buffer.from(expected));
}

Events

Zapier: Catch Hook

1. Start a Zap with the trigger Webhooks by Zapier → Catch Hook and copy its URL. Keep it private: anyone with it can post to your Zap.
2. In Settings → Webhooks, add that URL with the events you want.
3. On the webhook’s page, Send test event; in Zapier, Test trigger finds it, and later steps can use its fields.

Make: Custom webhook

1. Start a scenario with Webhooks → Custom webhook, add a webhook and copy its address.
2. In Settings → Webhooks, add that address with the events you want.
3. Click Redetermine data structure in Make, then Send test event on the webhook’s page: Make learns the fields from it.

Reference

Every route an API key may call, from the api’s OpenAPI 3.1 document at https://api.reachpool.ai/v1/openapi.json, which tools such as Postman can import. * marks what is required.