Webhooks

Webhooks allow you to receive real-time notifications about call events. Configure a webhook URL on your agent to receive HTTP POST requests when events occur.

Webhook Events

Event	When Triggered	Response Used
`assistant-request`	Before call is answered	Yes - can configure agent
`tool-calls`	Agent needs to execute a tool	Yes - return tool result
`status-update`	Call status changes	No
`end-of-call-report`	After call ends	No

Configuring Webhooks

Set the webhook URL and events on your agent:

Webhook Headers

All webhook requests include these headers:

Header	Description
`Content-Type`	`application/json`
`User-Agent`	`HMS-Sovereign/1.0`
`X-Webhook-Event`	Event type (e.g., `tool-calls`)
`X-Webhook-Timestamp`	Unix timestamp of the request
`X-Webhook-Signature`	HMAC-SHA256 signature (if secret configured)

Signature Verification

If you configure a webhook_secret, verify the signature to ensure requests come from Flireo:

Python:

Node.js:

Event Details

Assistant Request

Called before an inbound call is answered. Allows you to:

Customize the agent configuration per call

Personalize the greeting based on caller

Reject calls (e.g., outside business hours)

Timeout: 5 seconds. If your endpoint doesn't respond in time, the call proceeds with default configuration.

Response format:

{
  "agent_id": "uuid",  // Reference mode: use saved agent
  "agent": { ... },    // Transient mode: full agent config
  "agent_override": { ... }  // Hybrid mode: merge with agent_id
}

See Dynamic Assistant Configuration Webhook for payload details.

Tool Calls

Called when the agent needs to execute a custom tool during the conversation.

Timeout: 10 seconds for synchronous tools.

Response formats supported:

Object format: {"results": [{"tool_call_id": "...", "result": {...}}]}

Simple format: {"result": {...}}

Direct format: {...} (your data directly)

Error format: {"error": "message"}

See Tool/Function Call Webhook for payload details.

Status Update

Called when the call status changes:

in-progress - Call connected

ended - Call ended normally

ended-with-error - Call ended due to error

Response is ignored.

See Call Status Update Webhook for payload details.

End of Call Report

Called after the call ends with:

Call duration

AI-generated summary

Structured analysis (if analysis_plan configured)

Response is ignored.

See End of Call Report Webhook for payload details.

Common Payload Fields

All webhooks include this structure:

{
  "message": {
    "type": "status-update",
    "timestamp": "2025-12-13T12:00:00.000Z",
    "call": {
      "id": "5c4d030f-43e3-4e65-899e-8148521e660f",
      "type": "inbound_phone_call",
      "status": "in-progress"
    },
    "phone_number": {
      "number": "+31850835037",
      "name": "Flireo Demo"
    },
    "customer": {
      "number": "+31612345678"
    },
    "agent": {
      "id": "agent-uuid",
      "name": "Customer Support Agent",
      "llm_config": { ... },
      "tts_config": { ... },
      "stt_config": { ... }
    }
  }
}

Best Practices

Respond quickly - Return 200 OK as fast as possible, especially for status updates

Process asynchronously - Queue heavy processing for later

Verify signatures - Always verify webhook signatures in production

Handle retries - Implement idempotency for duplicate deliveries

Log everything - Keep webhook logs for debugging

Custom Tools Guide - Building tools for your agent

Call Analysis Guide - Structured post-call data

Webhook Security - Securing your webhooks

Webhook Events#

Configuring Webhooks#

Webhook Headers#

Signature Verification#

Event Details#

Assistant Request#

Tool Calls#

Status Update#

End of Call Report#

Common Payload Fields#

Best Practices#

Related#