Skip to main content

📘 How to Send Inbound RTB Requests to Your Moja Buyer

Bid request, ping, RTB

E
Written by Eric Gardona

A guide for publishers and sellers of RTB phone calls

Introduction

Your buyer is using the Moja call tracking platform and has enabled Inbound RTB for their campaign.
As a publisher, you will send inbound RTB bid requests to the unique inbound RTB endpoint they provide.

💡 Important
You will receive one unique inbound RTB endpoint per campaign.
If you work with the same buyer across multiple Moja campaigns, you will have multiple endpoints—one for each.

This guide explains exactly how to format and send your RTB requests.

🔗 1. Your Inbound RTB Endpoint

Your buyer will provide you with a URL that looks like this:

https://rtb.moja.cloud/inbound_rtb/{inbound_rtb_id}?CALLER_ID={{19995551234}}

This endpoint is unique to you and should be used only for the campaign it was issued for.

Example endpoint provided by your buyer:

https://rtb.moja.cloud/inbound_rtb/inbound_rtb_1762757680608_v5hjq8?CALLER_ID={{19995551234}}

🚀 2. How to Send Inbound RTB Requests

GET with query-string parameters is the recommended default because it is easiest to inspect, share, and troubleshoot. Moja can also accept POST requests, including JSON payloads, when a publisher integration requires it.

Request Format

https://rtb.moja.cloud/inbound_rtb/{inbound_rtb_id}?CALLER_ID={{19995551234}}&tag=value

Use the full endpoint URL, including https://. Replace the sample caller ID value with the caller ID value or variable from the sending platform. Use CALLER_ID as the standard caller ID parameter. CID is also supported.

Formatting Rules

✔️ Correct

  • First parameter starts with ?

  • Additional parameters begin with &

  • Use tag=value formatting

  • URL encoding recommended

❌ Incorrect

  • Do NOT use brackets: [CALLER_ID]

  • GET query-string requests are recommended by default; POST requests, including JSON payloads, may be supported when required by the publisher integration

  • Do NOT send malformed or nested parameter strings

Example Request

https://rtb.moja.cloud/inbound_rtb/inbound_rtb_1762757680608_v5hjq8?CALLER_ID=9999999999&CALLER_ZIP=99999&PUBLISHER_ID=subID

📇 3. Required Parameters

Moja strongly recommends sending:

Required

  • CALLER_ID — the caller’s phone number

  • ZIP_CODE or CALLER_STATE — Not required but should be sent if available

Moja can derive ZIP and State from phone number area code, but supplying your own may be more accurate for your buyer.

🧩 4. Optional Metadata You Can Send

You may include any additional fields your buyer requires, such as:

  • Publisher or Sub-ID

  • Traffic source

  • Channel or media

  • Lead/session ID

  • Campaign name or identifier

  • Custom Tags used for reporting, pass-through, or Advanced Filtering

  • Call context

  • Caller attributes you have available

💡 Tip
You can send any parameter you want, as long as it follows tag=value formatting.

Inbound parameters can be captured and passed through to your buyer. If your buyer wants to filter or route on custom values such as sub_id, lead_type, traffic_source, or vertical, those values should be defined as Custom Tags in Moja and then used in Advanced Filtering on Targets or RTB endpoints.

🎯 5. How Moja Uses Your Inbound Data

Moja automatically processes system-level fields:

Value

Description

CALLER_ID

Caller’s phone number

ZIP_CODE

Derived if not supplied

CALLER_STATE

Derived if not supplied

🔄 6. What Happens After You Send the RTB Request?

Here is the process your inbound request triggers:

Step 1 — You send the inbound RTB request

Includes CALLER_ID, ZIP, and any metadata.

Step 2 — Moja captures your data

ZIP/state may be derived if missing.
​

Step 3 — Moja rtb responds with a bid if qualified

Example bid response:

{"success":true,"request_id":"165b3f3a-5301-4ea1-a74c-66bf352481d1","allocation_time_seconds":60,"eligible_routes":[{"number":"+17014919171","payout":57.6,"payout_condition":"call_length_connected","payout_condition_duration":60}],"total_routes":1,"allocated_count":1,"timestamp":"2025-11-21T01:10:47.890Z"}

Step 4 — Moja accepts the call to the dynamic telephone number if your system accepts the bid

Moja accepts calls and connects if the call is sent within the allotted time

🧪 7. Testing Your RTB Integration to your Moja Buyer

You may test your RTB delivery using a browser for GET requests, or tools like cURL/Postman for GET and supported POST requests:

  • Web browser

  • cURL

  • Postman

Example test via browser:

https://rtb.moja.cloud/inbound_rtb/inbound_rtb_17627576555580608_v5hjq8?CALLER_ID=1234567890

Review call-level RTB details

After a call is created from RTB activity, you can review the related bidding activity from the call itself. Go to Reporting / Call Logs, open the call details panel, then check Call Life or the dedicated RTB tab.

This view is useful when you need to confirm whether RTB ran, which bid or route won, and whether any request/response step returned an error, timeout, no-bid, or below-minimum result.

🆘 Need Help?

If you need assistance formatting your inbound RTB requests or confirming delivery with your buyer:

👉 Contact your Moja-integrated buyer directly, or
👉 Request that they open a ticket with Moja Support on your behalf

Moja Support can only assist the buyer-side customer, not the publisher directly.

Did this answer your question?