The friction
Nightly CSV exports and API polling to keep systems in sync.
With Moja
Events pushed the second they happen, in the shape you defined.
Platform · Data in & out
Your data doesn't live here. It flows through.
Every call event can push to your systems the moment it happens, and your systems can push data in before the call routes. Webhooks run both directions, carry the fields you choose, and log every exchange.
Data-out is part of the foundation's contract: the platform proves what it sees by sending it to you, raw, in real time.
The working path
From input to next step.
Out on events, in before routing, logged both ways.
- 01
Out: call events push to any endpoint.
Four triggers — on incoming call, on answered, on converted, on hangup — fire webhooks to any URL with any HTTP method, GET through DELETE. Headers, query parameters, and body format (JSON, form data, or custom) are yours to define per webhook.
- 02
The payload writes itself from tags.
Dynamic tags drop call data into the payload — call ID, caller, campaign, publisher, buyer, duration, payout, revenue, conversion time. Your CRM gets the fields it expects, named the way it expects them, without middleware doing the translation.
- 03
In: enrich the call before it routes.
Incoming webhooks accept data while the call is still being set up, and that data becomes tags — alongside tags from RTB parameters, landing pages, and SIP headers. A call flow can then route on what your systems know: is this a homeowner, what's their age, have we seen this lead before.
- 04
Every exchange is logged.
Full request and response logs — headers, query parameters, bodies — kept separately for incoming and outgoing traffic. When an integration misbehaves, you read the actual exchange instead of reconstructing it from both vendors' support tickets.
Product specifics
The controls behind the work.
The webhook toolkit, stated plainly.
Four event triggers
On incoming call, on answered, on converted, on hangup.
All HTTP methods
GET, POST, PUT, PATCH, DELETE.
Custom payloads
JSON, form data, or custom formats; headers and query params too.
Dynamic tag insertion
Call, campaign, publisher, buyer, and revenue fields on demand.
Incoming enrichment
Pre-call data becomes routable tags before the call connects.
Tag sources
RTB parameters, landing pages, SIP headers, incoming webhooks.
Per-webhook auth keys
Unique authentication key on every webhook URL.
Configurable lifespan
Incoming webhook windows tuned per use, down to seconds.
Bidirectional logs
Full request/response history, incoming and outgoing separated.
Why connect it
Change the working pattern.
Webhooks replace polling, exports, and translation middleware.
The friction
Middleware services translating between the platform's format and yours.
With Moja
Dynamic tags build the payload your endpoint already accepts.
The friction
Routing decisions made blind to what your CRM knows.
With Moja
Pre-call enrichment turns your data into tags the flow routes on.