The public schemas describe these selections. They do not establish a released socket protocol, SDK subscription method, delivery order, or replay mechanism.
Choose an event design
Use client events to plan what the interface needs to display. Use client-to-server context to define what a supported client may submit. Use post-call webhooks for server-side notification preparation. Document the event’s owner, required fields, privacy classification, conversation identifier, and failure behavior. Treat external event data as untrusted input. Separate displaying an event from authorizing an action based on it.Frequently asked questions
Are event names proof of delivery?
Are event names proof of delivery?
No. Verify the released transport, emitted payload, authorization, and failure behavior before implementing a subscription.
Can a client event replace a post-call notification?
Can a client event replace a post-call notification?
They serve different recipients and lifecycle points. Choose the supported path for the job rather than assuming identical timing or persistence.