Webhooks

AI4CALL can call URLs you configure for call-related outcomes. The configuration accepts http:// or https:// URLs; use HTTPS in production, validate the expected JSON shape, and correlate events with your own request or call record.

Outbound result callback

Set callResultUrl when starting an outbound call. AI4CALL sends:

{
  "internal_id": "<YOUR_CORRELATION_ID>",
  "dialstatus": "ANSWER",
  "duration": 42
}

The callback reports the outbound outcome only; it does not contain a conversation transcript.

Conversation and post-call configuration

Configure the end-of-conversation endpoint with PATCH /assistants/{assistantId}/runtime/hangup/conversation-webhook:

{
  "enabled": true,
  "url": "https://example.com/hooks/ai4call",
  "authName": "crm-bearer"
}

authName is the name of an authentication already saved for the customer. Its credentials are resolved server-side and never travel in the request. Send authName: null to send without authentication; disable the integration with enabled: false.

Configure structured data extraction with PATCH /assistants/{assistantId}/runtime/hangup/schema:

{
  "hangupUrl": "https://example.com/hooks/extracted-data",
  "schema": [{
    "name": "customerIntent",
    "type": "string",
    "description": "Primary reason for the call",
    "required": true
  }]
}

Schema property types are string, number, boolean, enum, and object. Configure post-call MCP separately through /runtime/postcall/mcp-config.

Do not assume an HMAC signature is sent: webhook signing is not part of the current contract. Consult the API Reference for the exact configuration payloads.