Account
Lead counts by stage
Org-wide counts across the qualification pipeline. Excludes archived leads.
Authorization
bearerAuth AuthorizationBearer <token>
An API key from Settings → Integrations → Webhook (org admins only), sent as Authorization: Bearer rf_org_….
The scope is ranked — a key satisfies any requirement at or below its own tier:
read— see leads, conversations, transcripts and handoffs. Never changes anything.write— create and update leads, claim and resolve handoffs.admin— mint and revoke tokens, and change org-wide integration settings.
There is no approve scope. It was a rung once; it is not one now, and a key requested with it is rejected.
Tokens are org-scoped: one sees every agent's leads in its org. There is no project dimension. The token is shown once at creation and stored only as a hash.
In: header
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/v1/stats/leads"{ "object": "lead_stats", "total": 412, "new": 37, "qualifying": 88, "qualified": 143, "meeting_booked": 22, "nurture": 61, "not_qualified": 44, "closed": 17}