---
title: "Send Event"
method: POST
path: "/peopleevents/2/persons/{personId}/definitions/{definitionId}/events"
tags: ["customer-engagement", "people", "events"]
---

# Send Event

`POST /peopleevents/2/persons/{personId}/definitions/{definitionId}/events`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/peopleevents/2/persons/{personId}/definitions/{definitionId}/events`
- Auth: one of:
  - HTTP basic
  - API key in header `Authorization`
  - API key in header `Authorization`
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`

Use this endpoint to track events that persons perform. Your request must refer to existing person profile and [event definition](https://portal.infobip.com/people/events/definitions).

## Path parameters

- `definitionId` string, required
- `personId` string, required

## Query parameters

- `identifierType` 'ID' | 'EXTERNAL_ID' | 'PHONE' | 'EMAIL' | 'LINE' | 'FACEBOOK' | 'TELEGRAM' | 'PUSH' | 'WEB_PUSH' | 'LIVE_CHAT' | 'VIBER_BOTS' | 'INSTAGRAM' | 'INSTAGRAM_DM' | 'TWITTER' | 'APPLE_BUSINESS_CHAT' | 'KAKAO_SANGDAM' | 'GOOGLE_BUSINESS_MESSAGES' | 'WHATSAPP' | 'ZALO_FOLLOWER' | 'TIKTOK_BM', required
- `createPerson` boolean

## Request body

- Fadcd3a5e2560b383cc614bf34d902f536c2b4a12ddd61a5d337e7d4f40ab864EventResourceRequest
  - `eventId` string, nullable: Unique identifier of the event. If provided, it helps prevent duplicate events in case of retries—for example, if the first API call fails and the same event is sent again. Passing the same `eventId` ensures the event is only recorded once in the person profile.<br>The value must be `1–36` characters long and can include letters `(A–Z, a–z)`, digits `(0–9)`, underscores `(_)`, and hyphens `(-)` only.
  - `properties` object, nullable: Object containing event properties. Must match the corresponding event definition. See People Events [documentation](https://www.infobip.com/docs/people/events#properties-custom-events) for supported data types.
  - `interactionId` string, nullable: Identifier that correlates the event with a specific interaction (for example, a journey or a conversation). When provided, it is stored in the event metadata and can be used to match the event to the interaction it belongs to.

## Response `201`

Successfully created

- B3ed157de85ce51bb7c17933fb84ff4b3e9bcb9fb8576a5ae189b97589d5bd1cEventResourceResponse
  - `eventId` string: Unique identifier of the event.
  - `definitionId` string: Unique identifier of event schema.
  - `occurredTime` string, date-time: Time of event occurrence, as the following format: yyyy-MM-dd'T'HH:mm:ss.SSSZ
  - `properties` object, nullable: Object that contains event properties.
  - `metadata` object, nullable: Object that contains metadata of event occurrence.

## Other responses

- `400`: Invalid resource representation
- `401`: Unauthorized
- `403`: Forbidden
- `404`: Not Found
- `500`: Internal Server Error

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)