Reply First

The Reply First API is how your CRM or backend pushes leads in and keeps them in sync. It pairs with the outbound webhook — the API is how you write to Reply First, the webhook is how Reply First tells you what changed.

The base URL is https://replyfirst.ae. All requests use an org-scoped bearer token; all bodies are JSON.

There's no SDK yet — call the API directly with fetch, requests, or curl. The examples throughout show all three.

Authenticate

Create a token at Settings → Integrations → Webhook, then send it as a bearer token:

curl https://replyfirst.ae/api/v1/leads/3f1c2e00-9a1b-4c77-8d2e-2b6a1f0e9c34 \
  -H "Authorization: Bearer $RF_ORG_TOKEN"

See Authentication for token management, and Rate limits for the 120/minute cap.

Endpoints

Method	Endpoint
`POST`	`/api/v1/leads`	Create a lead
`GET`	`/api/v1/leads/{leadId}`	Get a lead
`PATCH`	`/api/v1/leads/{leadId}`	Update a lead

Reference

Authentication

Create, send, and revoke org tokens.

Errors

The error envelope and status codes.

Rate limits

120 requests/minute per token.

Webhooks

Signed events for the other direction.

API Reference