Your call ID · InboundX docs

With the ping (the usual way)

Send it on every ping, under any of these names:

ringba-requestidringba_requestidrequest_idcall_idcallidsourcecallidsource_call_idtraceexternal_idclickid

After the call starts

Some platforms create their call ID only when the call reaches them. Send it to us then:

GETPOSThttps://app.inboundx.io/api/rtb/call-id

curl

curl -X POST "https://app.inboundx.io/api/rtb/call-id" \
  -d "key=YOUR_PING_KEY" \
  -d "caller_number=+15555550123" \
  -d "request_id=abc-123"

We find the call by the caller's number, so send the same number you pinged with.

Answers

Every answer is HTTP 200 with JSON.

Status	What it means
`ok`	Attached. The answer says whether we found the call itself or the bid still held for it: callreservation
`no_match`	We found no recent call or held bid for that caller on this key. Check the number.
`error`	The request itself was wrong. The answer says what: missing_keymissing_caller_numbermissing_request_idbad_caller_numberlookup_failedunknown_keypublisher_mismatch

The three answers look like this:

JSON

{"status":"ok","matched":true,"via":"reservation"}
{"status":"no_match"}
{"status":"error","reason":"missing_key"}

Without a call ID

A postback URL that uses only {PHONE} still works, but it can't tell two calls from the same caller apart. Send a call ID whenever your platform has one.