Do not treat webhook relays and event webhooks as interchangeable. A relay is an inbound delivery path; an event webhook is an outbound notification from Vida.
Configure inbound email
Inbound email policy belongs to the selected Agent account:- Read
GET /api/v2/email/inboundPolicy?targetAccountId=.... - Choose
allowlistfor controlled senders oropenwhen any sender should be accepted. - Add approved addresses through
POST /api/v2/email/inboundWhitelistbefore enabling allowlist mode. - Update the policy with
PUT /api/v2/email/inboundPolicy. - Re-read both policy and allowlist, then send a representative email from an authorized address.
allowlist. Confirm the exact address and re-read the list after removal.
Deliver Vida events to your system
The Webhooks API supportsconversation, incoming, contact, agent, and onboarding event types. Create a separate destination when different systems own different event categories.
Vida sends JSON with these verification headers:
X-Vida-EventX-Vida-TimestampX-Vida-Signature-VersionX-Vida-Signature
410 Gone may be removed automatically, so use 410 only when the endpoint is permanently retired.
Read the webhook list after creation or deletion. Use a representative event to verify both delivery and your handler’s account attribution before relying on it in production.
Configure an inbound webhook relay
- List supported relay types with
GET /api/v2/webhookRelay/types. - Read the current configuration for the selected type.
- Create or update only a supported type with an HTTPS destination you control.
- Re-read it and send a safe provider test event.