Any CRM, call tracker or automation tool that can post JSON can send data to RankUpside. Won deals go to the revenue webhook and calls or form leads go to the lead webhook. Each client site has its own key, sent as a bearer token. One request can carry up to 500 items, and bad items return their own error.
What it doesn't do: The webhook only receives. It doesn't pull from your CRM or write anything back to it.
Updated
Won deals go to POST /api/hooks/revenue with the client site's key as a bearer token. Send one deal as an object or up to 500 as an array. Webhook
POST /api/hooks/revenue Authorization: Bearer rk_•••••••• { "id": "D-1042", "date": "2026-10-14", "landing_page": "https://copperlinegutters.example/", "amount": 4200, "status": "won", "source": "organic" }
{ "ok": true, "inserted": 1, "updated": 0, "errors": [] }| Field | Also accepted | If missing |
|---|---|---|
| id | external_id | A stable id from the deal's contents |
| date | – | Today |
| amount | value | Rejected: amount is required |
| landing_page | landingPage, url | Listed as unmatched |
| status | won, open or lost | Won |
| source | – | Counted and flagged |
| phone, email | – | Optional, for matching calls and leads |
Calls and form leads go to POST /api/hooks/leads?provider=… with the same key. The provider tells the parser which shape to read: callrail, whatconverts, generic or quo.
POST /api/hooks/leads?provider=generic
Authorization: Bearer rk_••••••••
{
"id": "CALL-3391",
"date": "2026-10-09T15:42:00Z",
"type": "call",
"landing_page": "https://copperlinegutters.example/services/gutter-repair",
"source": "google / organic",
"duration": 157,
"phone": "+1 202-555-0142"
}| provider | Reads |
|---|---|
| callrail | CallRail's call payload as it's sent |
| whatconverts | WhatConverts Phone Call and Web Form leads |
| generic | id, date, type, landing_page, source, duration, phone or email |
| quo | Quo call.completed events; outbound calls are skipped, not errors |
CallRail and WhatConverts webhooks take a URL only, so the key goes in the URL as a key parameter: /api/hooks/leads?provider=callrail&key=rk_… The settings page shows that form for those two.
More on this:CallRailWhatConvertsWebhook docs
Each client site has its own key, shown in Client settings › Leads & revenue by its last four characters. New key stops the old one right away, so update the tool that posts.
| Case | Status | Response |
|---|---|---|
| Every item saved | 200 | ok true, with inserted and updated counts |
| Some items bad | 200 | ok false; the good items are saved and errors lists the bad ones |
| Every item bad, or the body isn't JSON | 400 | ok false, with the errors |
| Missing or unknown key | 401 | Nothing saved |
| More than 500 items | 413 | Nothing saved; split the batch |
Step-by-step setups for the tools agencies ask about most, each with its field mapping.
More on this:No webhook? Upload a CSVWhat the deals add to a reportClick-share attributionAttribution docs
Client settings › Leads & revenue lists the last 15 deals received and the latest calls and leads. Each call tracker has Send test lead, which posts a fictional test lead so you can see it arrive before a real one does.
Recent deals
Received by webhook · Copperline Gutters
The first report builds from 13 weeks of Search Console history as soon as you connect. Start with 3 client sites.
Weekly search report · Copperline Gutters
Sep 14 – Oct 11, 2026 vs the 4 weeks before
Copperline Gutters got 27 clicks from named buyer searches in the last 4 weeks, up 23% from the 4 weeks before. Google hides the search terms behind 84% of all 289 search clicks. Rankings rose across the site: pages that steadily show up are up about 2.4 positions.