Events

An event is a named notification definition. When you call POST /v1/send/welcome, Sendivent looks up the welcome event and uses its templates to create a delivery.

Events define the available templates. Routing chooses which one is used at send-time.

What Events Are For

Define notification types (welcome, password-reset, order-shipped)
Define which channels are available for each notification
Attach templates per channel (and optionally per language)

Creating Events

Go to Events in your dashboard
Click Create Event
Fill in:

Field	Description	Example
Name	URL-friendly identifier	`order-confirmation`
Display Name	Human-readable name	Order Confirmation
Channels	Available delivery methods	Email, SMS, Slack, Push, Telegram, WhatsApp, Discord

Templates are configured per channel (and optionally per language). See Templates.

Event Naming

Use clear, lowercase names with hyphens:

welcome
password-reset
order-shipped
invoice-ready
team-invite
verification-code

Avoid names like notification1 or email-v2.

Sending to an Event

bash

curl -X POST "https://api.sendivent.com/v1/send/welcome" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "user@example.com",
    "payload": { "name": "Alice" }
  }'

Common Pitfalls

Event doesn't exist — create it in the dashboard before sending
Missing template — add a template for the channel you expect to deliver
Invalid name — use order-shipped, not order shipped
Blank variables — ensure payload includes keys used in the template

Events ​

What Events Are For ​

Creating Events ​

Event Naming ​

Sending to an Event ​

Common Pitfalls ​

See Also ​