---
title: "Send a Messages API event"
method: POST
path: "/messages-api/1/events"
tags: ["platform", "messages-api", "sending-message"]
---

# Send a Messages API event

`POST /messages-api/1/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/messages-api/1/events`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`
  - API key in header `Authorization`
  - API key in header `Authorization`
  - HTTP basic

Send one or more events to multiple recipients.

An event is an interaction with end-user's device which does not impact messaging content of conversation.

Examples of events are: TYPING_STARTED, TYPING_STOPPED.

## Request body

- 899caf445aab842b03fe1d74e4afd7097f0161dae66538ffa05bba2f153d708fMessagesApiEventRequest
  - `events` 899caf445aab842b03fe1d74e4afd7097f0161dae66538ffa05bba2f153d708fMessagesApiOutboundEvent[], required: Array of event objects of a single event or multiple events sent
    - `event` 'TYPING_STARTED' | 'TYPING_STOPPED' | 'SEEN', required: Event type.

## Response `200`

OK

- 899caf445aab842b03fe1d74e4afd7097f0161dae66538ffa05bba2f153d708fResponseEnvelopeMessageResponseMessageResponseDetails
  - `bulkId` string: Unique ID assigned to the request if messaging multiple recipients or sending multiple messages via a single API request. If not provided, it will be auto-generated and returned in the API response. Typically used for fetching delivery reports and message logs.
  - `messages` 899caf445aab842b03fe1d74e4afd7097f0161dae66538ffa05bba2f153d708fMessageResponseMessageResponseDetails[], required: An array of message objects of a single message or multiple messages sent under one bulk ID.
    - `messageId` string: Unique message ID. If not provided, it will be auto-generated and returned in the API response.
    - `status` 899caf445aab842b03fe1d74e4afd7097f0161dae66538ffa05bba2f153d708fMessageStatus: Indicates the [status](https://www.infobip.com/docs/essentials/response-status-and-error-codes#api-status-codes) of the message and how to recover from an error should there be any.
      - `groupId` integer: Status group ID.
      - `groupName` 'ACCEPTED' | 'PENDING' | 'UNDELIVERABLE' | 'DELIVERED' | 'EXPIRED' | 'REJECTED': Status group name that describes which category the status code belongs to, i.e., [PENDING](https://www.infobip.com/docs/essentials/response-status-and-error-codes#pending-general-status-codes), [UNDELIVERABLE](https://www.infobip.com/docs/essentials/response-status-and-error-codes#undeliverable-general-status-codes), [DELIVERED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#delivered-general-status-codes), [EXPIRED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#expired-general-status-codes), [REJECTED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#rejected-general-status-codes).
      - `id` integer: Status code ID.
      - `name` string: [Status code](https://www.infobip.com/docs/essentials/response-status-and-error-codes#api-status-codes) name.
      - `description` string: Human-readable description of the status.
      - `action` string: Action to take to recover from the error.
    - `destination` string: The destination address of the message, i.e., its recipient.
    - `details` 899caf445aab842b03fe1d74e4afd7097f0161dae66538ffa05bba2f153d708fMessageResponseDetails: Other details of the message.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `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)