Docs / Point your call tracker at the lookup URL · 8 min
Point your call tracker at the lookup URL
TrackDrive, Ringba, or anything that can fire a webhook per call. Retreaver has its own guide.
Your lookup URL
Every workspace gets one lookup URL, shown on the home page. Your tracker POSTs the inbound caller number to it before the call routes, and the response says allow or block.
- Send POST with body caller_number={caller_number}&api_key=YOUR_KEY. Form-encoded and JSON bodies both work.
- The response is JSON: fraud_check is "allow" or "block", and fraud_check_comments carries the reason (line type and verdict).
- Route on fraud_check: allow continues to your buyers; block sends the call to a dead-end target or drops it.
TrackDrive
- Offer → Integrations → add a caller lookup webhook that fires on incoming call.
- Set the method to POST, the URL to your lookup URL, and the body to caller_number={caller_number}&api_key=YOUR_KEY.
- Add a routing rule on the response field fraud_check equals block to reject the call.
Ringba
- Campaign → Call Flow → add a webhook node before your target group.
- POST the [tag:InboundNumber] to your lookup URL with your api_key.
- Branch the flow on the fraud_check response value: allow proceeds, block routes away.
A lookup that fails or times out answers allow: an outage on the scoring path never blocks a genuine caller.