RCS over API
___

RCS, available over [Conversations API](https://www.infobip.com/docs/conversations-api), [Messages API](https://www.infobip.com/docs/messages-api), and [RCS API](https://www.infobip.com/docs/api/channels/rcs), offers a convenient way for you to send messages. However, it's crucial that you familiarize yourself with [compliance and guidelines](https://www.infobip.com/docs/guidelines-and-compliance), as well as the details of [message types](https://www.infobip.com/docs/message-types), before utilizing RCS messaging APIs.
___

## Outbound messages

Send text, file, card, or carousel as your RCS message.

RCS Message templates can be used in India only. To use it, you must follow [guidelines](https://www.infobip.com/docs/message-types#rcs-template-messages-india-only-).
___

## Messages status reports

Fetch delivery reports for RCS messages.

You can generate reports for delivered and seen messages using different parameters.
___

## Inbound messages

Use this method to receive RCS messages and streamline two-way communication.

Messages received could be text, file, location, and suggestion.

NOTE
Media files sent by end users in [mobile originated (MO)](https://www.infobip.com/glossary/mo-mobile-originated) messages, such as JPG or PDF files, are available for 60 days. After 60 days, Rich Communication Services (RCS) deletes these files from the cache.

___