Use POST /v1/events/send to record a workspace event and optionally update the related contact in the same request.

​
What happens when you send an event

For the public Event API path, MailKatana:
  1. resolves or creates the contact
  2. persists the event
  3. merges contact properties from the request
  4. syncs mailing list membership when supplied
  5. runs synchronous event side effects in the same transaction
That means delayed template jobs are scheduled immediately when a matching rule exists, but the future email send still happens later in the separate template-delivery worker.

​
Example

curl -X POST https://api.mailkatana.com/v1/events/send \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "avery@example.com",
    "eventName": "user_registered",
    "eventProperties": {
      "source": "checkout"
    },
    "contactProperties": {
      "email_verified": false,
      "plan": "starter"
    },
    "mailingLists": {
      "welcome_list": true
    }
  }'

​
When to use events vs transactional send

  • Use events when you want MailKatana automation or delayed template rules to react to business activity.
  • Use transactional send when you already know which saved template you want to send right now.