Developer platform
Assume every webhook can be delayed, duplicated, or forged.
CXRove treats signatures, timestamps, event identities, tenant context, schema versions, and feature state as admission requirements—not validation after processing.
Direct answer
How should CXRove webhooks be consumed?
Webhook consumers should verify the signature, timestamp, source, event ID, tenant binding, schema version, feature state, and replay window before processing. The same event can arrive more than once or out of order, so processing must be durable, idempotent, and reconcilable.
Verify before processing
Bound the raw request, preserve the exact signature input, check signature and timestamp, and match the source to expected provider or CXRove configuration.
Persist event identity before side effects
A durable ledger rejects altered replay, returns the prior result for an identical completed event, and serializes concurrent deliveries.
Derive tenant binding from server state
A provider account, endpoint, subscription, or event binding resolves to one organization through trusted configuration—not caller metadata.
Design for retries and reconciliation
A sender may retry after a timeout even when processing succeeded. Reconciliation compares authoritative states without caller-supplied proof.
Keep webhook logs secret-safe
Record event handles, source, schema, status, timing, and safe errors. Exclude signing secrets, full headers, raw bodies, payment data, transcripts, and credentials.
Common questions
Answers for a practical evaluation.
Are webhook deliveries exactly once?
No network delivery should be assumed exactly once. Use at-least-once-safe idempotency and reconciliation.
Can provider metadata select the tenant?
No. Tenant binding must resolve from trusted endpoint or account configuration.
How are webhook endpoints configured?
Organization administrators configure destinations and signing material inside the protected workspace. The public contract documents verification, replay, retry, and reconciliation behavior without exposing secrets.
Continue exploring
Related CXRove guidance.
Next action
Turn a customer conversation into a completed next step.
Choose an Agent capacity, define the first workflow, and decide what the Agent may know, do, and hand to a person.