---
title: "Create an event"
method: POST
path: "/events"
tags: ["Events"]
---

# Create an event

`POST /events`

Create an event to track a contact's interaction.

## Request body

- Event
  - `event_name` string, required — The name of the event that occurred. This is how you will find your event in Brevo. Limited to 255 characters, alphanumerical characters and - _ only.
  - `event_date` string — Timestamp of when the event occurred (e.g. "2024-01-24T17:39:57+01:00"). If no value is passed, the timestamp of the event creation is used.
  - `identifiers` EventIdentifiers, required — Identifies the contact associated with the event. At least one identifier is required.
    - `email_id` string — Email Id associated with the event
    - `phone_id` string — SMS associated with the event
    - `whatsapp_id` string — whatsapp associated with the event
    - `landline_number_id` string — landline_number associated with the event
    - `ext_id` string — ext_id associated with the event
  - `contact_properties` object — Properties defining the state of the contact associated to this event. Useful to update contact attributes defined in your contacts database while passing the event. For example: **"FIRSTNAME": "Jane" , "AGE": 37**
  - `event_properties` object — Properties of the event. Top level properties and nested properties can be used to better segment contacts and personalise workflow conditions. The following field type are supported: string, number, boolean (true/false), date (Timestamp e.g. "2024-01-24T17:39:57+01:00"). Keys are limited to 255 characters, alphanumerical characters and - _ only. Size is limited to 50Kb.

## Response `204`

An event posted

## Other responses

- `400` — bad request
- `401` — unauthorized

---

[API](https://skmtc.net/getbrevo/apis/brevo-api.md) · [All operations](https://skmtc.net/getbrevo/apis/brevo-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/getbrevo/brevo-api/revisions/2aec3cf66501/schema)