CallerSift

Docs / Every platform at a glance · 3 min

Every platform at a glance

All eight trackers plus custom webhooks: where each request is configured and what it sends.

Every platform's request at a glance

Each platform has its own merge tag for the inbound caller number and its own place to configure the request; the contract is identical everywhere. The linked guide walks through each dashboard step by step.

PlatformWhere it's configuredCaller token / body
[TrackDrive](/docs/trackdrive-setup)Outgoing webhook, Method POST (Custom Body), JSON body + Content-Type header{"caller_number": "[caller_id]", "api_key": "fck_your_key"}
[Ringba](/docs/ringba-setup)Ring Tree Target → Request Settings, POST JSON{"caller_number": "[tag:InboundNumber:Number]", "api_key": "fck_your_key"}
[Retreaver](/docs/retreaver-setup)Campaign webhook (Start trigger), URL query or Webhook Configuratorcaller_number=[caller_number]&api_key=fck_your_key
[CallTrackingMetrics](/docs/calltrackingmetrics-setup)CTM Lambda (routes on the verdict) or webhook (tags only){"caller_number": "{{caller_number}}", "api_key": "fck_your_key"}
[Phonexa](/docs/phonexa-setup)External Connector block in the Call Logic IVR, Params tabcaller_number = caller phone placeholder, api_key as a Post param
[CallRail](/docs/callrail-setup)Webhook into a small relay you host (CallRail can't customize bodies)relay forwards customer_phone_number
[Invoca](/docs/invoca-setup)Custom Webhook (data) or Real-Time Routing webhook (gating)calling_phone_number substitute parameter + static api_key
[boberdoo](/docs/boberdoo-setup)Outside Services tab, wired by boberdoo supportcaller_number (E.164) + api_key, form or JSON
Custom webhookAnything that can POST per inbound callcaller_number=+15551234567&api_key=fck_your_key

GET requests are not supported; the endpoint only answers POST. There is no SDK to install and no other endpoint to call: this one URL is the entire integration surface.

Ready to try it against real leads?

Start screening