Inbound webhooks allow you to send data to MojaAI from your systems. Use these webhooks to pass caller metadata before a call is routed, update revenue on completed calls, or manage custom tags for reporting and attribution.

What you can do with inbound webhooks:

📢 Tag & Parameter Normalization — Updated March 2026

Inbound webhook tags and request parameters are normalized and populated before routing-plan resolution and call-flow execution. This means variable and tag nodes in your call flow can reliably read inbound RTB query parameters, body fields, and header values as tags — including data sent via the call_data webhook.

Header tag extraction expanded: Tag extraction from request headers now processes all request headers — not just X--prefixed ones. If you previously relied on non-X--prefixed headers being excluded from tag extraction, review your tag configuration. No action is required for most integrations — this fix is automatic.

Each inbound webhook has a unique authentication key. Include the key as a query parameter in your requests:

The moja_auth_key parameter is required on every request. Requests without a valid key will return a 401 Unauthorized error.

MojaAI supports four types of inbound webhooks, each with its own endpoint and request structure:

Use the call_data webhook to pass caller metadata into MojaAI. This data is matched to incoming calls by caller ID and can be used for routing decisions, custom tags, and reporting.

POST https://webhooks.moja.cloud/call-data?moja_auth_key={auth_key}

Any additional fields you send (beyond caller_id and transaction_id) are stored with the request. When a call comes in from the matching caller ID, fields that correspond to custom tags you've defined in MojaAI are automatically applied to the call.

Success (200 OK)

When a call arrives, MojaAI checks for call_data webhook requests that match the caller's phone number. If a match is found, the data from the webhook is applied to the call. The lookback window is configurable per webhook (default: 15 days).

Typical flow:

Use the update_revenue webhook to update revenue amounts on completed calls. This is useful when conversions happen after the call ends (e.g., a sale closes days later).

POST https://webhooks.moja.cloud/update-revenue?moja_auth_key={auth_key}

Identify the call by call_log_id:

Or identify the call by phone_number:

*Either call_log_id or phone_number must be provided. If both are provided, call_log_id takes priority.

Success (200 OK)

Use the update_tags webhook to add or remove custom tags on calls.

POST https://webhooks.moja.cloud/update-tags?moja_auth_key={auth_key}

Adding tags:

Removing tags:

Adding and removing in the same request:

*Either call_log_id or phone_number must be provided.

**At least one of add or remove must be provided.

Success (200 OK)

Use the update_fields webhook to update multiple call record fields in a single postback request. This is a unified webhook type that accepts any combination of supported field updates — revenue, conversion status, tags, publisher payouts, and more.

POST https://webhooks.moja.cloud/update-fields?moja_auth_key={auth_key}

GET https://webhooks.moja.cloud/update-fields?moja_auth_key={auth_key}&call_log_id={id}&{fields}

All fields are optional — include only the ones you want to update:

Note on tag operations [VERIFY]: Based on the latest code review, tag operations (add and remove) may need to be wrapped under a tags key (e.g., tags.add / tags.remove). Verify the payload format against your integration before relying on a specific structure.

Fields can be sent at the top level or nested inside a fields object. Calls are identified by call_log_id or phone_number.

Example — Top-level fields (POST):

Example — Tag operations using tags wrapper [VERIFY format]:

Example — GET request:

Note: The existing update_revenue and update_tags webhook types continue to work exactly as before. The update_fields type is an additional option — no changes needed to existing integrations.

As of April 3, 2026, the update_revenue, update_tags, and update_fields webhook types support batch updates — you can now update up to 50 calls in a single request by passing call_log_id as an array instead of a single string.

All existing single-ID requests continue to work exactly as before. Batch support is a backward-compatible addition.

Pass call_log_id as a JSON array. Everything else in the request stays the same — the same field values are applied to every call in the array.

Single call (existing — unchanged):

Batch (new):

A batch request response includes two fields:

Always check failed_call_log_ids in the response. A single invalid or unrecognized ID will not block the rest of the batch — failed IDs are reported separately so you can retry them individually.

Batch update_revenue:

Batch update_tags:

Batch update_fields:

Batch updates are well-suited for:

Note: Incoming webhooks have a rate limit of 100 requests per minute per webhook configuration. With batch support, a single request can update up to 50 calls — keep this in mind when designing high-volume integrations.

To update revenue or tags, you need either the call_log_id or the caller's phone_number.

The call_log_id uniquely identifies a specific call. You can obtain it from:

1. Outbound webhook payloads — Include the [CALL_ID] tag in your outbound webhook template:

2. URL parameters — Configure your target to append the call ID to a redirect URL or form submission.3. Dashboard — Find the call log ID in your call logs in the MojaAI dashboard.

When you provide phone_number instead of call_log_id, MojaAI looks up recent calls from that phone number within the configured lookback window. This can match multiple calls if the same caller has made more than one call within the window.

Lookback window: Configurable per webhook (1–7 days, default: 7 days).

All three webhook types support idempotent requests using the transaction_id field. When you include a transaction_id:

This prevents duplicate processing when retrying failed requests.

Rate limits are configurable per webhook and can be set to per-minute, per-hour, or per-day periods. Contact your account manager if you need a higher limit.

Problem: Getting "Missing caller_id parameter" on call data webhook

Problem: Getting "Call log not found" on update revenue or tags

Problem: Getting "Unauthorized" error

Problem: Revenue update not reflected in reports

Problem: Tags not appearing on calls