Brilo AI webhook payloads are delivered as structured JSON in an HTTP POST to your configured webhook endpoint. The payload includes event types (for example: call started, transcript available, or call ended), a unique call session identifier, timestamps, and optional transcription or intent data when enabled. Brilo AI sends standard HTTP headers and can be configured to include a signature header for verification; retry behavior and delivery headers follow the webhook settings you configure. Use JSON parsers on your side to read event types, metadata, and nested transcription objects.

What format are Brilo AI webhook payloads sent in?

Brilo AI webhook payloads are sent as JSON in an HTTP POST and include event types, timestamps, and call session metadata.

Are Brilo AI webhook payloads JSON or XML?

Brilo AI webhook payloads use JSON by default; XML is not the standard delivery format.

How does Brilo AI deliver call data to a webhook?

Brilo AI posts JSON payloads with event names, session IDs, and optional transcription fields to your webhook URL.

Buyers ask about webhook payload formats because they need to map incoming data into existing systems—CRMs, case management, or downstream analytics—in regulated environments. Knowing the schema and delivery guarantees affects security checks, data parsing code, and compliance reviews in healthcare, banking, and insurance. Clear payload expectations reduce integration time, limit errors, and make it easier to build safe escalation and audit workflows.

When configured, Brilo AI sends webhook payloads as HTTP POST requests with a JSON body describing the event and related objects. Events represent discrete moments in the call lifecycle (for example: call_initiated, transcription_ready, call_completed). Brilo AI includes a consistent call session identifier so you can correlate multiple events from the same interaction. The webhook payload is the JSON object sent to your endpoint containing event metadata, timestamps, and optional call content. Event type is the string that identifies what happened and drives routing and processing logic. Parse the JSON, inspect the event type, and route or persist records in your system accordingly.

Brilo AI webhook payloads do not automatically push full audio files unless you enable audio export and your account and configuration allow it; by default, payloads carry metadata and transcription snippets. Brilo AI can be configured to include a verification signature header, but you must implement signature validation on your endpoint to authenticate payloads. The webhook signature is an optional delivery header used to validate that an incoming POST came from Brilo AI; it is not validated on your behalf. Brilo AI will not bypass configured routing rules or send sensitive PII fields unless you enable those fields explicitly in your integration settings. If you require stricter delivery guarantees (for example, guaranteed ordering or persistent queues), implement idempotency checks using the session identifier and design your webhook endpoint to acknowledge receipts promptly.

Brilo AI webhook events are commonly used to trigger a human handoff: when the agent emits an event such as escalation_requested or low_confidence_intent, your webhook can create a ticket, page a human agent, or call an internal API to open a live transfer. Use the session identifier and last_event timestamp in the payload to present context to the human agent (recent transcript fragments, detected intent). If you prefer, configure Brilo AI to pause automation and wait for an explicit API or webhook-driven signal from your system before resuming automated handling.

When available, see Brilo AI’s integration guidance for example mappings and supported event types on the HubSpot integration page for a reference integration pattern: Brilo AI HubSpot integration and automated lead logging.

Using Brilo AI webhook payloads reduces manual data entry by feeding structured call events directly into downstream systems. You can automate post-call workflows—follow-ups, CRM updates, or claims intake—without building polling infrastructure. For regulated teams, predictable JSON payloads and session identifiers help create auditable trails and make it simpler to apply redaction, retention, and review rules in your backend systems.

What data formats are included in the webhook payload?

Brilo AI webhook payloads are JSON objects containing event metadata, timestamps, a session identifier, and optional fields such as transcription text, detected intents, and confidence scores when those features are enabled.

Can I receive audio via webhooks?

Audio is not typically embedded in the JSON payload. Brilo AI can be configured to provide audio exports or download links as part of events when your account and settings permit, but you should plan to fetch large media assets from a secure storage link rather than receiving them inline.

How should I validate incoming webhook requests?

If you enable the Brilo AI webhook signature feature, validate the signature header against the secret you configure in Brilo AI. Additionally, use TLS, IP allowlists, and idempotency checks based on the session identifier to ensure secure and reliable processing.

What happens if my endpoint returns an error?

Brilo AI will retry delivery according to its retry policy (backoff and retry attempts). Design your endpoint to return appropriate HTTP status codes (2xx for success) and implement idempotent handling so retries do not create duplicate records.

Can I customize which events Brilo AI sends?

Yes. Configure event subscriptions in your Brilo AI project to receive only the event types you need (for example: transcription_ready, call_completed, or escalation_requested) to reduce noise and simplify downstream logic.