Skip to main content
Configure how inbound calls are handled for an agent identity. This config is keyed on the agent identity, so it governs inbound handling for both dedicated numbers and shared iMessage lines that route to that identity. Requires an admin API key, an identity-scoped API key, or you can manage this from the Inkbox Console.

Set incoming call action

Upsert the inbound-call configuration for an agent identity.

Request body

"hosted_agent" — answer with Inkbox Voice AI — requires neither URL. URL fields sent alongside it are stored but ignored while the action is "hosted_agent". "forward" sends the call to one phone number or SIP URI without opening an Inkbox media WebSocket. Connected forwarded calls use inbound and outbound call minutes simultaneously. SIP targets must use the exact sip:user@public-dns-host[:port] form; sips:, IP or private/single-label hosts, credentials, parameters, and URI headers are not accepted. Inkbox does not substitute the number that was called. SIP username/password authentication and custom SIP headers are not supported. Secure signaling and media settings are managed by Inkbox. Omitted forwarding fields preserve their saved values. To clear a saved target, set forwarding_target_type to null; this clears both forwarding destinations. Sending only the active destination field as null while preserving its target type returns 422. Because the forward action requires a destination, switch incoming_call_action away from forward in the same request when clearing its target. Existing WebSocket and webhook URL fields retain their replacement behavior, so include the URLs you want to keep when changing those actions.

Request example

JSON

Response (200)

JSON

Error responses

Code examples


Get incoming call action

Read the inbound-call configuration for an agent identity.

Query parameters

Response (200)

JSON

Error responses

Code examples


Incoming call action object


  • Inkbox Voice AI — what answers the call when the action is "hosted_agent"
  • Calls — place outbound calls and inspect where inbound calls were forwarded
  • Webhooks — when the action is "webhook", the webhook responds with {action, client_websocket_url} to accept or reject the call (see the phone Webhooks page)
  • Media Stream — how audio and text flow over the WebSocket once a call is answered