May 2026

Release Notes: 2026-05-04 — API — Expanded Moja Public API Reporting

Expanded Moja Public API reporting for RTB activity, webhook request history, and call lifecycle timelines.

Released: May 4, 2026

Available on: Premium and Enterprise plans

More reporting visibility. Directly through the API.

Moja has expanded the Moja Public API with additional reporting access for teams that need deeper visibility into RTB activity, webhook request history, and call-level event timelines.

If your team monitors traffic, investigates request outcomes, audits webhook delivery, or needs to connect Moja reporting data into internal tools, this release gives you more of that visibility programmatically.

What You Can Do

Inbound RTB reporting

Review inbound RTB request activity through the API.
Inspect request-level reporting data without relying only on the UI.
Support operational reviews, troubleshooting, and customer follow-up from your own systems.

Outbound RTB reporting

Review outbound RTB request activity through the API.
See request-level details that help explain downstream outcomes.
Use the data to support partner, buyer, and routing performance analysis.

RTB request details

Look up details for specific RTB requests.
Review request activity and related outcomes in a structured format.
Use API-accessible reporting data to support faster investigation workflows.

RTB life-log events

Access life-log style event history for RTB requests.
Review the sequence of events associated with a request.
Use the timeline to help understand what happened during request processing.

Incoming webhook request history

Review incoming webhook request activity.
Inspect request and response visibility for troubleshooting.
Use request history to help diagnose configuration, delivery, and integration issues.

Outgoing webhook request history

Review outgoing webhook activity through the API.
Inspect delivery details and response information.
Support operational monitoring for webhook-based workflows.

Call lifecycle timelines

Access call-level event timelines through the API.
Review the sequence of events associated with a call.
Use lifecycle visibility to support troubleshooting, QA, and customer support workflows.

How It Works

Authentication: API key in the request header.
Format: JSON over HTTPS.
Access: Organization-scoped API access through the existing Moja Public API.

No new authentication flow is required. These reporting capabilities are available through the same Moja Public API access pattern your team already uses.

Interactive API Documentation

You can review the available API documentation from your Moja account:

Go to My Account.
Open the Organization tab.
Find the Moja API section.
Select View API Documentation.

The documentation includes available resources, request structure, authentication expectations, and response examples.

Call log cost and attribution fields

Call log reporting now includes additional cost and route-attribution fields for margin analysis and downstream reporting.

cost_per_min — carrier rate per billable minute, shown in USD per minute.
rtb_id / rtb_name — populated when the call was routed through an RTB source.
target_id / target_name — populated when the call was routed through a target.

Other route types return null for the dedicated attribution fields. Existing dial_type, dial_type_id, and dial_name fields remain available for backward compatibility.

In Call Log reporting exports, Cost/min is exported as Cost/min (USD) when present. Per-call carrier cost preserves sub-cent precision where applicable, and Moja Magic zero-cost behavior remains unchanged.

Getting Started

Confirm API access is enabled for your organization.
Open the API documentation from your Moja account.
Review the reporting resources available to your team.
Use your existing API key authentication pattern to begin querying reporting data.

Note: Access is organization-scoped, so returned data is limited to the organization associated with the API key.

What’s Not Included

No reporting UI changes are included in this release.
No custom dashboard builder is included.
No authentication changes are required.

Expanded Moja Public API reporting is available on Premium and Enterprise plans.

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

Originally published at https://help.mojaai.com/en/articles/14906498-release-notes-2026-05-04-api-expanded-moja-public-api-reporting

Release Notes: 2026-05-06 — DNI — Dynamic Number Routing and Attribution Reliability Improvements

Dynamic-number routing and attribution reliability improvements for campaign number changes.

Customer Release — Dynamic Number Routing and Attribution Reliability Improvements

Release date: May 6, 2026

Release type: Bug fix / reliability improvement

Product area: Dynamic Number Pools, Snippets, Campaign Routing

Dynamic number routing and attribution reliability improvements

We released improvements to keep dynamic-number routing and attribution aligned when campaign numbers are moved or updated after a snippet has already been created.

This helps reduce cases where dynamic-number calls could continue routing or reporting against an older campaign assignment after the default campaign number was moved.

What changed

More reliable dynamic-number routing — Dynamic-number calls now use the current campaign associated with the snippet’s default number whenever possible.
Improved attribution alignment — Call attribution follows the same campaign resolution logic, helping call tracking stay aligned with the current campaign setup.
Safer snippet configuration — Snippet default-number selections are validated so users cannot save a default number that is not currently routable.
Better campaign update handling — Campaign number changes now keep matching active snippets aligned going forward.

Customer impact

Dynamic-number calls are less likely to route through an outdated campaign after campaign number changes.
Call tracking and attribution are more consistent with the current campaign setup.
Ops teams have safer snippet configuration behavior when selecting or updating default numbers.
Customers using dynamic number pools get more reliable campaign routing after number moves or campaign updates.

Where to find it

These improvements apply to dynamic number pool routing, snippet default-number configuration, campaign number changes, and related call attribution behavior.

Notes

No customer action is required for the routing and attribution improvements.
If a default number is not routable, users may be asked to select a valid campaign number before saving snippet configuration changes.

Originally published at https://help.mojaai.com/en/articles/15037674-release-notes-2026-05-06-dni-dynamic-number-routing-and-attribution-reliability-improvements

Release Notes: 2026-05-07 — DNI — Dynamic Number Call Tracking Visibility Improvements

Improved call tracking visibility for dynamic-number calls connected to landing page data.

Customer Release — Dynamic Number Call Tracking Visibility Improvements

Release date: May 7, 2026

Release type: Bug fix / reporting reliability improvement

Product area: Dynamic Number Pools, Landing Pages, Call Tracking

Dynamic number call tracking visibility improvements

We improved call tracking visibility for dynamic-number calls connected to landing page data.

What changed

More complete tracking visibility — Dynamic-number calls that previously may not have appeared in tracking views can now be included when landing page data is available.
Improved landing page call details — Landing page call details can be recovered more reliably for these calls.
Better attribution coverage — Tracking reports should better reflect calls tied to dynamic number replacement flows.

Customer impact

Teams get a more complete view of call activity and attribution when using dynamic numbers on landing pages.
Ops teams can review dynamic-number call activity with more confidence.
Customers using dynamic number replacement flows should see more consistent reporting coverage.

Where to find it

These improvements apply to tracking and reporting views for dynamic-number calls connected to landing page data.

Originally published at https://help.mojaai.com/en/articles/15037669-release-notes-2026-05-07-dni-dynamic-number-call-tracking-visibility-improvements

Release Notes: 2026-05-08 — AI Agents — Voice Agents Setup and LLM Configuration Improvements

Improvements that make Voice Agents easier to find, duplicate, configure, and test.

Voice Agents Setup and LLM Configuration Improvements

Release date: May 7–8, 2026

Release type: Bundled enhancement

Product area: Voice Agents

Voice Agents setup and configuration improvements

We released a set of improvements that make Voice Agents easier to find, duplicate, configure, and test. The update includes clearer Voice Agents naming, a new clone workflow, voice previews, improved duration editing, refreshed advanced configuration controls, and a cleaner LLM model picker/default model flow.

What’s new

Clearer Voice Agents navigation and labels — The product now uses more specific Voice Agents naming across the relevant navigation and setup areas, making it easier for users to identify the right workspace.
Clone Agent workflow — Users can duplicate an existing Voice Agent’s core setup instead of rebuilding the same configuration from scratch.
Voice previews — Users can preview available voices from the voice picker before saving or testing an agent.
Improved Max Duration editing — The Max Duration field now behaves more naturally when users clear and retype values.
Advanced Settings improvements — Advanced controls are easier to access, while LLM-specific configuration can be shown only where enabled.
Refreshed LLM picker — The model picker is cleaner and easier to scan, with updated model metadata, grouping, labels, and default model behavior.

Customer impact

Faster setup for customers and Ops teams creating similar Voice Agents.
Less trial-and-error when choosing voices.
Clearer navigation and terminology for Voice Agent workflows.
Easier editing when adjusting Voice Agent duration settings.
Better control over which organizations can access LLM-specific configuration.
More consistent default behavior when creating or updating Voice Agents.

Where to find it

Users can find these improvements in the Voice Agents setup and edit experience, including the Voice Agent list, create/edit forms, voice picker, advanced settings, and LLM configuration controls.

Notes

No customer action is required for the naming, picker, and form behavior improvements.
Access to LLM-specific configuration may depend on organization-level enablement.
Cloning copies the core Voice Agent setup, but some connected resources may still need to be configured separately after cloning.

Originally published at https://help.mojaai.com/en/articles/15037507-release-notes-2026-05-08-ai-agents-voice-agents-setup-and-llm-configuration-improvements

Release Notes: 2026-05-08 — RTB — Inbound RTB Request Performance Steps

More RTB Log Life detail for inbound RTB request troubleshooting.

Customer Release — Inbound RTB Request Performance Steps

Release date: May 8, 2026

Release type: Enhancement

Product area: Reporting, Inbound RTB

Inbound RTB request performance steps

We improved the RTB Log Life view so teams can see more of the activity connected to a specific inbound RTB request.

What changed

New RTB detail tabs — The RTB Log Life detail panel now includes additional tabs for the RTB response and related RTB requests.
Outbound RTB request visibility — Teams can see outbound RTB requests connected to a specific inbound RTB request, grouped by RTB group.
Buyer request details — Grouped request details can show the buyer, request status, payout, request ID, and start/end timing where available.
Step-level troubleshooting data — Step details can show request method, request URL, response code, duration, configuration, response data, and error details when present.
Inbound response visibility — The response tab surfaces the RTB response sent for the inbound request when one is available.

Customer impact

Faster troubleshooting for RTB performance and response issues.
Better visibility into buyer request activity tied to an inbound request.
Clearer review of request status, response details, payouts, timing, and errors from the reporting page.
Easier investigation when customers ask what happened with a specific inbound RTB request.

Where to find it

Users can find these improvements in Reporting → RTB Log Life.

Originally published at https://help.mojaai.com/en/articles/15037673-release-notes-2026-05-08-rtb-inbound-rtb-request-performance-steps

Release Notes: 2026-05-08 — Routing — Call Flow JavaScript Node Improvements

Improvements to JavaScript node editing and call-flow branching reliability.

Customer Release — Call Flow JavaScript Node Improvements

Release date: May 8, 2026

Release type: Bug fix / usability improvement

Product area: Call Flows

Call Flow JavaScript node improvements

We improved JavaScript nodes in the call-flow builder to make advanced call-flow logic easier to edit and more reliable during live call routing.

What changed

Improved JavaScript editing experience — JavaScript nodes now provide a stronger editing experience for multiline scripts.
Clearer function structure — The editor more clearly shows the function structure users are working within.
Smoother tag insertion — Tags can be inserted more naturally while editing JavaScript logic.
More reliable branching — JavaScript node success and failure paths now route more reliably through the call flow.

Customer impact

Teams can build and maintain custom call-flow logic with less friction.
Success and failure branches behave more predictably during live call execution.
Ops teams have a cleaner editing experience when configuring advanced call-flow behavior.

Where to find it

These improvements apply to JavaScript nodes in the call-flow builder.

Originally published at https://help.mojaai.com/en/articles/15037668-release-notes-2026-05-08-routing-call-flow-javascript-node-improvements

Release Notes: 2026-05-11 — Platform — Product Updates

MojaAI product updates released May 11, 2026.

Release: May 11, 2026 — MojaAI Product Updates

:rocket: Enhancement — Call recording controls by entity

Release date: May 11, 2026

Location: Campaigns, Publishers, Buyers, Buyer Targets, RTB Targets

What changed

Networks can now control whether calls are recorded for specific campaigns, publishers, buyers, buyer targets, and RTB targets.

Each supported page now includes a Recording Settings section with a Record Calls checkbox. Recording remains enabled by default. To stop recording for a specific part of the routing path, uncheck Record Calls on the applicable entity.

If any applicable entity in the routing path is set not to record, the call will not be recorded.

Customer impact

Gives networks more control over recording behavior for compliance, partner requirements, and account-specific call handling.

Notes

This release covers recording enable/disable controls. Separate permissions for buyers or publishers to view recordings are not included in this release.

:bug: Bug fix — RTB response parsing for nested array fields

Release date: May 11, 2026

Location: Campaign → Outbound RTB / RTB Targets

What changed

Fixed an RTB response parsing issue where mapped values inside nested array fields could fail to resolve correctly.

This improves routing reliability for RTB integrations where bid, duration, or other mapped values are returned inside nested response structures.

Customer impact

Valid RTB responses that rely on nested array fields can now be parsed correctly, reducing failed routing caused by missing mapped values.

Notes

Formula mappings that reference unusual field names may still need the correct mapping syntax.

:rocket: Enhancement — Number Pool column on Numbers list

Release date: May 11, 2026

Location: Numbers list

What changed

The Numbers list now shows which Number Pool a number belongs to.

Admins can see a new Number Pool column directly in the Numbers list, making it easier to identify pool-assigned numbers without opening each number individually or cross-referencing pool settings.

Customer impact

Improves number management for teams working with multiple number pools.

Notes

Admin users can open the linked number pool from the Numbers list where applicable. Publisher-facing views keep number pool details hidden by default.

:bug: Bug fix — More reliable call recording playback

Release date: May 11, 2026

Location: Reporting → Call Log / call recording playback and export

What changed

Fixed an issue where a small percentage of call recordings could appear unavailable even though the recording existed.

Recording playback and export links now locate recordings more reliably for calls where the recording is associated with the call completion date rather than the call start date.

Customer impact

Reduces “recording not available” cases in call logs and improves reliability when playing or exporting call recordings, especially for calls that cross date boundaries.

Originally published at https://help.mojaai.com/en/articles/15072662-release-notes-2026-05-11-platform-product-updates

Release Notes: 2026-05-11 — RTB — Inbound RTB Response Options

Inbound RTB now includes response options for max responses, sorting, and sort direction.

Customer Release: Inbound RTB Response Options

Release date: May 11, 2026

Type: Enhancement

Location: Campaign —> Inbound RTB

What’s new

Inbound RTB publisher setup now includes response options that let you control how eligible route responses are returned.

You can now set:

Max responses — limit how many eligible routes are returned.
Sort by — order responses by payout or duration.
Sort direction — return results in ascending or descending order.

Why it matters

This gives teams more control over Inbound RTB response behavior directly from the publisher setup, making it easier to match response output to each partner or traffic workflow.

Customer impact

Customers using Inbound RTB can now:

Return only the number of eligible responses they need.
Prioritize eligible routes by payout or duration.
Set saved defaults while still allowing request-level overrides when needed.

Notes

Request URL parameters can override the saved response options for an individual request.

Originally published at https://help.mojaai.com/en/articles/15064268-release-notes-2026-05-11-rtb-inbound-rtb-response-options