Skip to main content

Webhook Postbacks: Multi-Field Call Updates

D
Written by Denise Abdullah
Updated today

FEATURE ENHANCEMENT RELEASE

Location: Webhooks → Incoming
​Release Date: March 27, 2026

We've introduced a powerful new webhook type — update_fields — that lets you update multiple call record fields in a single postback request. No more chaining separate revenue and tag updates — handle everything in one call.

What's New

  • update_fields Webhook Type — A new unified incoming webhook type that accepts any combination of field updates in one request.

The following fields can be updated on an existing call record:

  • converted (boolean) — Mark a call as converted or remove conversion status

  • call_converted_at (datetime or null) — Set an explicit conversion timestamp

  • revenue_paid_out (number) — Override the revenue payout amount

  • publisher_paid_out (number) — Override the publisher payout amount (completed calls only)

  • reason (string or null) — Set or clear the call reason/disposition

  • no_payout_reason — Set or clear a payout hold reason. Values: Campaign preconversion, Condition not met, Caps exceeded, or null (completed calls only)

  • add (object or array) — Add or update tags on the call

  • remove (string or string[]) — Remove tags by key

GET and POST Support — Send postbacks via POST (JSON body) or GET (query parameters). GET support is useful for simple integrations, tracking pixels, or systems that can only fire a URL. GET is also now available on the existing update_revenue and update_tags endpoints.

Flexible Payload Structure — Fields can be sent at the top level or nested inside a fields object — both formats work. Calls can be identified by call_log_id or phone_number.

Live and Completed Call Support — Postbacks work regardless of call state. Completed calls are updated directly. For live/active calls, updates are queued and applied when the call completes.

Why This Matters

Handle conversion + revenue + disposition + tags in a single request instead of managing multiple webhook configs. GET support opens the door to simpler integrations that don't require building a POST request.

Example Use Cases

  • A lead management system sends a single postback when a lead converts: sets converted, revenue, and reason — all in one request

  • A tracking pixel fires a GET URL with revenue and conversion data as query parameters

  • A CRM updates publisher payouts and hold reasons on completed calls for billing reconciliation

Getting Started

  1. Navigate to Webhooks → Incoming → Create

  2. Select type update_fields

  3. Copy the generated auth key and endpoint URL

  4. Configure your external system to send POST or GET requests with the call identifier and fields to update

  5. Test with a completed call to verify fields are updated correctly

Note: The existing update_revenue and update_tags webhook types continue to work exactly as before.

Coming Soon

A future release will add support for batch updates — sending multiple field updates across multiple calls in a single request. Stay tuned.

Questions? Reach out to your account manager or contact support.

Did this answer your question?