Integrate Refer2u CRM data into your tools with profile-scoped API keys and signed webhooks.
Generate an API key from Dashboard → Integrations → Developer API. Send it as a Bearer token on every request:
Authorization: Bearer ru2_live_your_api_key
Each key is scoped to one Refer2u profile. All data returned belongs to that profile only.
https://www.refer2u.com/api/v1
120 requests per minute per API key. When exceeded, the API returns 429 Too Many Requests with a Retry-After header.
| Resource | Endpoints |
|---|---|
| Contacts | GET/POST /contacts · GET/PATCH/DELETE /contacts/:id · GET /contacts/search |
| Companies | GET/POST /companies · GET/PATCH/DELETE /companies/:id · GET /companies/search |
| Partners | GET/POST /partners · GET/PATCH/DELETE /partners/:id · GET /partners/search |
| Connections | GET/POST /connections · GET/PATCH/DELETE /connections/:id · GET /connections/search |
| Webhooks | POST /hooks/subscribe · DELETE /hooks/:id · GET /hooks/sample/:eventType |
Subscribe to events via POST /api/v1/hooks/subscribe. Payloads are signed with HMAC-SHA256 in the X-Refer2u-Signature header.
Supported events:
Machine-readable API definition available at /openapi.json.
Third-party applications can use OAuth 2.0 to connect on behalf of users. The authorisation flow starts at /api/oauth/authorize and presents a consent screen where users choose which profile to grant access to.
Partner app registration is currently available to Refer2u administrators via POST /api/oauth/apps.
Use the same API keys with the official Refer2u Zapier app. See Integrations → Zapier for setup instructions.