Run a menu key's HTTP request once, from the settings screen (F15-E2)
POST/api/channels/:channel/calls/ivr/lookup-test
Makes the request an action: lookup menu key would make, and returns
what came back — status, elapsed time, body and, when the body is whole
JSON, the parsed document. The point is the dot paths: the operator
picks variables off a real response instead of naming them from
memory and finding out on a live call.
Our servers make this request, so it carries every restraint the call
path carries — the same SSRF policy as webhooks, enforced at validation
AND again at request time against a hostname that changed its answer in
between, no redirect following, and the same low timeout ceiling — plus
a per-user rate limit (20/min) and a cap on how much of the response
comes back. Admin-gated (Channel update).
A dead endpoint or a 500 is an ANSWER, not our failure: it comes back
as 200 with ok: false. The only 422 is a url we refuse to dial.
Request
Responses
- 200
- 422
What the tenant's endpoint answered — including a refusal of theirs.
The url resolves somewhere we will not dial (ivr_lookup_unsafe_url).