Skip to main content
This page shows the different webhook formats we send for events.
All webhook requests includes X-CEKURA-SECRET header with your configured webhook secret.
Non-binary metrics use type (continuous_qualitative, numeric, or enum) with a numeric or enum score.Binary metrics use eval_type: "binary" with a boolean passed (true = pass, false = fail). Use these fields when integrating.For backward compatibility, binary metrics also still include the deprecated legacy fields type: "binary_workflow_adherence" and score: 5/0 (not shown in the examples below). These will be removed in a future version — new integrations should rely on eval_type and passed.
Webhook JSON Example:

Pre-run Notifications

Sent once at the start of a run, before any calls are dispatched. Use it to provision or configure your external test environment (seed data, feature flags) for the evaluators about to run — for example, enabling appointment cancellation in a sandbox business before your cancellation evaluators run. The run waits for your endpoint to respond before dispatching calls (30s timeout, retried up to 3 times), so the sandbox is ready before the first call. Enable it with the Pre-run Webhook toggle in your project’s webhook settings. Each entry in runs carries the scenario, the resolved test_profile (its information holds your main_agent_variables), the personality, and the phone_number for that run. The X-CEKURA-IDEMPOTENCY-KEY header is set to result_pre_trigger:<result_id> so retries can be de-duplicated.

Result Notifications

Cronjob Notifications

Call Log Evaluation Notifications

Webhook Forwarding