---
title: "Send RCS events"
method: POST
path: "/rcs/1/events"
tags: ["channels", "rcs", "rcs-outbound-events"]
---

# Send RCS events

`POST /rcs/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/rcs/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 RCS events to multiple recipients. Maximum request size is 10MB.

## Request body

- B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsEventRequest
  - `events` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsEvent[], required: An array of event objects of the events to be sent.
    - `sender` string, required: Identifier of an RCS sender that will be used to send event.
    - `destinations` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62ToDestination[], required: An array of destination objects for where the event is being sent. A valid destination is required.
      - `to` string, required: The destination address of the message.
      - `messageId` string: The ID that uniquely identifies the message sent.
    - `content` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsOutboundEventContent, required: Event content.
      - `type` 'SEEN' | 'TYPING_INDICATOR', required
    - `options` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsEventOptions: Event options.
      - `platform` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62Platform: Platform options. For more details, see [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
        - `entityId` string: Used when specifying an entity in outbound send requests. It is also returned in notification events. For detailed usage, refer to the [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
        - `applicationId` string: Used when specifying an application in outbound send requests. It is also returned in notification events. For detailed usage, refer to the [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
      - `deliveryTimeWindow` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62DeliveryTimeWindow: Sets specific message delivery window outside of which messages won't be delivered. Often, used when there are restrictions on when messages can be sent. The exact time of the day to start sending messages can be defined using the `from` property. The exact time of the day to end sending messages can be defined using the `to` property. Properties `from` and `to` should be both provided with the minimum 1 hour difference or omitted.
        - `days` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62DeliveryDay[], required: Days of the week which are included in the delivery time window. At least one day must be provided. Separate multiple days with a comma.
        - `from` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62DeliveryTime: The exact time of the day. The time is expressed in the UTC time zone.
          - `hour` integer, required: Hour when the time window opens when used in the `from` property or closes when used in the `to` property.
          - `minute` integer, required: Minute when the time window opens when used in the `from` property or closes when used in the `to` property.
        - `to` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62DeliveryTime: The exact time of the day. The time is expressed in the UTC time zone.
          - `hour` integer, required: Hour when the time window opens when used in the `from` property or closes when used in the `to` property.
          - `minute` integer, required: Minute when the time window opens when used in the `from` property or closes when used in the `to` property.

## Response `200`

OK

- B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62ResponseEnvelopeMessageResponseMessageResponseDetails
  - `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` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62MessageResponseMessageResponseDetails[], 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` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62MessageStatus: 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` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62MessageResponseDetails: Other details of the message.

## Other responses

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