Moja AIGo to portal →
Publisher integration guide

Connect to Moja RTB with confidence.

Paste your inbound RTB URL to generate a prefilled setup guide and validate a payload locally—without sending a live ping.

Safe to use for setup.Review your integration details and validate fields locally. This page does not submit RTB requests or route calls.

Suffix parameters are accepted, but the guide uses only the endpoint before the first “?”.

01

Your endpoint

Example endpoint

The endpoint below is a non-live example. Paste your assigned Moja URL above to replace it with your endpoint.

GET endpoint
https://rtb.moja.cloud/inbound_rtb/your-publisher-endpoint-id
Keep this URL private.The final path segment identifies your inbound RTB configuration. Share it only with the publisher implementing the integration.
02

Request flow

  1. 1
    Collect caller data

    Prepare the caller ID and any optional routing attributes available before the call.

  2. 2
    Send a GET request

    Add values as URL query parameters. Replace the entire {{PLACEHOLDER}} token—including both curly braces—with the real value.

  3. 3
    Read the response

    Use the returned eligibility and allocation details to decide the next routing step.

  4. 4
    Route the matching call

    Follow the production contract supplied with your Moja account; do not reuse an expired allocation.

03

Payload reference

GET · query string

This campaign requests the fields below. The local validator and request template follow this field schema.

ParameterUseDescriptionExample
CALLER_IDRequired for this campaignCaller phone number. E.164 (+12125550184) is preferred; CID may be supported by account configuration.+12125550184
FIRST_NAMEOptionalCaller first name.Jane
LAST_NAMEOptionalCaller last name.Doe
ZIP_CODEOptional5-digit US postal code or ZIP+4.10001
STATEOptional2-letter US state code.NY
Required: remove the double curly braces. Replace the whole token, including {{ and }}. For example, send CALLER_ID=+12125550184—never CALLER_ID={{+12125550184}}.
Copy-ready request template
https://rtb.moja.cloud/inbound_rtb/your-publisher-endpoint-id?CALLER_ID={{CALLER_ID}}&FIRST_NAME={{FIRST_NAME}}&LAST_NAME={{LAST_NAME}}&ZIP_CODE={{ZIP_CODE}}&STATE={{STATE}}
04

Response examples

Illustrative response shapes for integration planning. HTTP 200 or success: true means Moja processed the request—not that the caller data was validated or a route is available. Use eligible_routes to determine eligibility. Your account’s production contract is authoritative.

Eligible route
{
  "success": true,
  "request_id": "1d0db814-812a-4201-9d2e-4c64efffXXXX",
  "inbound_rtb_id": "inbound_rtb_1790807650364_b5e7XXXX",
  "allocation_time_seconds": 30,
  "eligible_routes": [
    {
      "number": "+18335553435",
      "payout": 8.24,
      "duration": 211
    }
  ],
  "total_routes": 1,
  "allocated_count": 1,
  "timestamp": "2026-10-01T21:59:54.324Z"
}
No eligible route
{
  "success": true,
  "request_id": "req_example_124",
  "eligible_routes": []
}
Request accepted, no eligible route
{
  "success": true,
  "request_id": "req_example_125",
  "eligible_routes": []
}
05

Payload lab

Local only
No live RTB request is sent.Values remain in this browser session only. Validation and URL construction happen entirely on this page.

Paste your assigned endpoint to enable validation.

Locally constructed request preview
https://rtb.moja.cloud/inbound_rtb/your-publisher-endpoint-id?CALLER_ID={{CALLER_ID}}&FIRST_NAME={{FIRST_NAME}}&LAST_NAME={{LAST_NAME}}&ZIP_CODE={{ZIP_CODE}}&STATE={{STATE}}
06

Share this guide

Generate the guide first, then share the hash link whenever possible. All exports and links contain the endpoint identifier.

Standalone HTML

A self-contained branded guide that works offline.

PDF guide

Opens the branded guide in your browser’s Save as PDF dialog.

Instructions file

Clean Markdown for Slack, email, or internal docs.