Pre-Bridge HTTP Checks for Call Routing
Released: July 8, 2026
MojaAI now supports configurable HTTP checks that run after a route or target has been selected, but before the call is bridged. This gives teams a way to validate compliance, eligibility, or buyer-specific requirements at the exact point where the platform knows which destination would receive the call.
Why it matters
Some checks should not happen before routing because the selected buyer or target is not known yet. Other checks should not wait until after the call is complete because the result may need to decide whether the call should connect at all.
Pre-Bridge Checks add that missing middle step: MojaAI can select the route first, run the configured external check, then decide whether to connect, reject, fail over, or follow timeout/error handling.
What’s included
Create and manage Pre-Bridge Checks from Webhooks → Pre-Bridge Checks.
Configure HTTP request details, timeout handling, response evaluation, and multiple response-field conditions.
Choose how the call should proceed based on pass, fail, error, or timeout outcomes.
Assign a Pre-Bridge Check to specific routing plan routes.
Reuse one check across multiple routes when the same endpoint and rules apply.
Configure separate checks per route or target when each buyer requires its own endpoint or validation logic.
Review call life-log details showing the selected route, check result, and routing decision.
Example 1: One shared compliance check
If the same validation endpoint and same pass/fail rules apply across the routing plan, a single Pre-Bridge Check can be created and reused.
Example: A customer wants to validate a TrustedForm or compliance token only after MojaAI has confirmed there is a selected route. In this case, one Pre-Bridge Check can call the customer’s validation endpoint, evaluate the response, and determine whether the call should connect, reject, or fail over.
Example 2: Buyer-specific checks
If each buyer or target requires its own endpoint, credentials, request format, or response rules, create a separate Pre-Bridge Check for each buyer-specific route.
Example routing plan:
Route 1 → Buyer A → Buyer A validation endpoint
Route 2 → Buyer B → Buyer B validation endpoint
Route 3 → Buyer C → Buyer C validation endpoint
Each route can have its own Pre-Bridge Check, allowing MojaAI to send the selected call data to the correct buyer-specific endpoint only after that buyer’s route has been selected.
How to set it up
To configure a Pre-Bridge Check, you’ll need the external validation endpoint MojaAI should call, including the request method, required headers, request body or query parameters, expected response fields, and the pass/fail rules that determine whether the call should connect, reject, or fail over.
Go to Webhooks → Pre-Bridge Checks.
Create the check using the endpoint, request details, timeout behavior, and response conditions.
Configure the desired outcomes for pass, fail, error, and timeout.
Open the relevant routing plan.
Assign the Pre-Bridge Check to the route where it should run.
If multiple targets require different endpoints or rules, create separate checks and assign each one to the corresponding route.
Place a test call and confirm the check runs after target selection but before the call bridges.
Availability: Available now in production.