Build on ReachHQ

Everything you run in the app is available programmatically. Drive it from your own code over a scoped REST API, from an AI assistant over the MCP server, or react to activity in real time with webhooks.

Base URLs & auth

Surface	Production	QA
REST API	`https://api.reachhq.io/api/v1`	`https://api.qa.reachhq.io/api/v1`
MCP server	`https://api.reachhq.io/mcp`	`https://api.qa.reachhq.io/mcp`

Authenticate every request with a workspace API key: Authorization: Bearer rhq_live_…. Each operation requires a specific scope, so a key only ever does what you granted it.

Three ways in

REST API

HTTP / JSON

A versioned, scoped REST API under /api/v1 covering the whole platform, with consistent pagination and typed errors.

MCP server

AI assistants

94 tools over Streamable HTTP. Connect Claude or ChatGPT and operate ReachHQ in natural language, scoped to your key.

Webhooks

Real-time events

A signed POST the moment an email is sent, opened, clicked, replied to, bounces, or a recipient unsubscribes.

Conversions

Attribution

Report signups, meetings and purchases back to the campaign that drove them with a CAPI-style postback or pixel.

Full API reference. Every endpoint, parameter and response is in the interactive reference.

Quickstart

Create an API key in the ReachHQ app under Settings › API keys, choosing the scopes it should carry. Then confirm it works:

bash

curl https://api.reachhq.io/api/v1/whoami \
  -H "Authorization: Bearer rhq_live_xxx"

# { "workspaceId": "ws_...", "scopes": ["campaigns:read", "leads:write", ...] }

Create your first lead:

bash

curl -X POST https://api.reachhq.io/api/v1/leads \
  -H "Authorization: Bearer rhq_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{ "email": "ada@example.com", "firstName": "Ada", "company": "Analytical Engines" }'

Keep reading

REST API guide: authentication, the full scope catalogue, pagination, errors and rate limits.
MCP server guide: connect Claude / ChatGPT and the complete 94-tool catalogue.
Webhooks guide: event types, payloads and signature verification.
Conversion tracking: the cid, the CAPI postback and pixel, and automatic signup conversions.
Interactive API reference: the live OpenAPI document.