CallGrid

WEBHOOKS AND POSTBACKS

Wire every call event into the systems you already run.

CallGrid webhooks push call events to your systems in real time, and postbacks let your buyers report conversions back, so every dollar of revenue ties to the exact call that earned it.

Trusted by enterprise call buyers and sellers. Uptime live on status.callgrid.com.

The postback round trip
CallGridCall events
TimeCallerSourceDurRevStatus
10:42(415) 555-0142Meridian Media4:12$42.00Billable
10:41(415) 555-0188Cardinal Leads6:03$58.50Billable
10:41(415) 555-0117Bluepeak2:47$36.00Converted
Routed callcaller and buyer
Your buyer's system
holding call_id
Caller qualifiesconverting

We pass a unique call ID on the dial. Your buyer returns it when the call converts, so revenue ties to the exact call.

THE PROBLEM

When call data lives in one tool and your CRM, ad platforms, and billing live in others, you reconcile by hand, conversions arrive late or never, and the revenue on a call never makes it back to the record that earned it.

Every hour spent stitching exports together is an hour not spent buying better calls. And every conversion that lands in the wrong place, or nowhere, is attribution you paid for and lost.

WEBHOOKS, OUTBOUND

Real-time call webhooks the moment something happens.

CallGrid fires an event the instant a call starts, connects, completes, or is marked billable or converted, so your systems react instantly instead of waiting on a batch.

call.completed
Call completed
sourceGoogle Ads
duration4:12
dispositionbillable
Your CRMDelivered
Ad platformDelivered
AnalyticsDelivered
Team chatDelivered

One event, fanned out to every system you connect. Illustrative.

Real time

No polling, no waiting. The event fires the moment it happens, so your systems are never behind the call.

Goes anywhere

Any endpoint that accepts an HTTP request. Your CRM, ad platforms, analytics, internal tools, and team chat.

Secure

Protect your endpoint with a shared secret or your own auth header, so you can trust every event that arrives.

Webhooks3New endpoint
EndpointEventsAuthLast deliveryStatus
https://your-crm.example.com/callscall.completedcall.convertedAuth header2m agoActive
https://hooks.your-app.example.com/ingestcall.startedcall.completedSecret14s agoActive
https://api.your-analytics.example.com/eventscall.completedSecret1m agoActive

POSTBACKS, INBOUND

Your buyers report conversions back to the exact call.

A pay per call postback closes the loop. CallGrid passes a unique call ID to the buyer on the dial, the buyer holds it in their system, and they return it when the call converts, so billing and payouts reflect what really happened.

1

We pass the call ID on the dial

Every call routed to your buyer carries a unique ID they can read.

2

The buyer holds it

Their system keeps the ID with the caller while the call plays out.

3

They return it on convert

The postback fires with the same ID, so the conversion attaches to the exact call.

Posting Instructions
Conversion, Generic
Parameters
ParameterDescriptionRequired
call_idThe unique ID of the callRequired
revenueRevenue earned on the callOptional
eventThe conversion event to reportOptional
API configuration
Platform
Parameters
Example
GET https://your-domain.example.com/postback?call_id={{call_id}}&revenue={{revenue}}&event={{event}}
View integration documentation
When a buyer has no platform

No tracking platform on the buyer side? We steer you to the setup that actually works.

If a buyer runs no call tracking platform at all, there is nothing on their end to capture the ID or fire a postback, so postbacks will not work for them. That is not a dead end. The right setup is fixed revenue and fixed duration on that destination instead, so your pricing stays deterministic per qualified call and you still get paid for the calls that matter.

Fixed revenue per qualified callFixed duration threshold

WHAT YOU CAN WIRE UP

Connect calls to the rest of your stack.

Optimize ad platforms on real calls

Sync conversions to your ad platforms and analytics, for example Google Ads and GA4, so you bid on the calls that convert instead of the clicks that do not.

Google AdsGA4Your analytics

Update your CRM

The instant a call lands, the record updates, so your team works from the truth.

Notify your team in chat

Send the calls that matter straight to the channel your team already watches.

Trigger your automations

Kick off whatever runs next, on your own tools, the moment an event fires.

Reconcile billing and payouts

Keep billing and payouts squared automatically as conversions come back.

Feed live dashboards

Stream events into your own dashboards so the numbers move with the calls.

BUILT TO BE RELIABLE

Delivered in real time, over HTTPS, secured by you.

Events are delivered the moment they happen over an encrypted connection. A little setup on your side keeps your records square no matter what.

Secure your endpoint

Use a shared secret or your own auth header so only trusted requests get through.

Make it idempotent

Key on the call ID so a repeated event is handled once, never double counted.

Reconcile any gap

Run a highly available endpoint, and poll the call API to square any gap so records always match.

Uptime is live on status.callgrid.com.

"The CallGrid team is a pleasure to work with. They connected to our Agent Availability API and built an integration in just a few hours. I cannot recommend this team enough."

Sean StanleyCallTools

WHERE IT FITS

Webhooks and postbacks close the loop.

Call Tracking captures the call and its tags, Routing and Real-Time Bidding decide where it goes, and webhooks and postbacks carry the result back out to your stack and back in from your buyers, while Reporting and the API give you the same data on demand.

FAQ

Webhooks and postbacks, answered

  • Webhooks push CallGrid call events out to your systems the moment they happen. Postbacks let your buyers report conversions back in. One carries events out to your stack, the other carries revenue back in from your buyers, so the full picture lands where you need it.

  • The key moments in a call's life. A call starts, a call connects, a call completes, and a call is marked billable or converted. Send the events your systems care about so they react in real time instead of waiting on a batch.

  • Protect your endpoint with a shared secret or your own auth header. Only requests carrying the secret or header you set are accepted, so you can trust that an event reaching your system really came from CallGrid.

  • CallGrid passes a unique call ID to the buyer on the dial. The buyer holds it in their system and returns it on the postback when the call converts, so the conversion attaches to the exact call that earned it and billing and attribution stay correct.

  • If a buyer runs no call tracking platform at all, there is nothing on their end to capture the ID or fire a postback, so postbacks will not work for them. Use fixed revenue and fixed duration on that destination instead, so pricing stays deterministic per qualified call.

  • Yes. Push call conversions back to your ad platforms and analytics so you optimize on real calls, not clicks. Wire the endpoints you already run and the events flow as calls happen.

  • It helps to have one wire up an endpoint, but you are not on your own. Our team supports the setup directly, the docs walk through every step, and most operators are live quickly. If you want a hand, we will get you connected.

Tie every dollar back to the call that earned it.