---
title: "Receives an incoming message"
method: POST
path: "/channels/messages/receive"
tags: ["Channels"]
deprecated: true
---

# Receives an incoming message

`POST /channels/messages/receive`

> **Deprecated.**

Adds a message to a conversation. To use the endpoint, you need to have **Messengers integration** OAuth scope enabled and the Messaging manifest ready for the [Messaging app extension](https://pipedrive.readme.io/docs/messaging-app-extension).

## Request body

- object
  - `id` string, required — The ID of the message
  - `channel_id` string, required — The channel ID as in the provider
  - `sender_id` string, required — The ID of the provider's user that sent the message
  - `conversation_id` string, required — The ID of the conversation
  - `message` string, required — The body of the message
  - `status` 'sent' | 'delivered' | 'read' | 'failed', required — The status of the message
  - `created_at` string, date-time, required — The date and time when the message was created in the provider, in UTC. Format: YYYY-MM-DD HH:MM
  - `reply_by` string, date-time — The date and time when the message can no longer receive a reply, in UTC. Format: YYYY-MM-DD HH:MM
  - `conversation_link` string, url — A URL that can open the conversation in the provider's side
  - `attachments` object[] — The list of attachments available in the message
    - `id` string, required — The ID of the attachment
    - `type` string, required — The mime-type of the attachment
    - `name` string — The name of the attachment
    - `size` number — The size of the attachment
    - `url` string, required — A URL to the file
    - `preview_url` string — A URL to a preview picture of the file
    - `link_expires` boolean — If true, it will use the getMessageById endpoint for fetching updated attachment's urls. Find out more [here](https://pipedrive.readme.io/docs/implementing-messaging-app-extension)

## Response `200`

The message was registered in the conversation

- object
  - `success` boolean — If the request was successful or not
  - `data` object
    - `id` string, required — The ID of the message
    - `channel_id` string, required — The channel ID as in the provider
    - `sender_id` string, required — The ID of the provider's user that sent the message
    - `conversation_id` string, required — The ID of the conversation
    - `message` string, required — The body of the message
    - `status` 'sent' | 'delivered' | 'read' | 'failed', required — The status of the message
    - `created_at` string, date-time, required — The date and time when the message was created in the provider, in UTC. Format: YYYY-MM-DD HH:MM
    - `reply_by` string, date-time — The date and time when the message can no longer receive a reply, in UTC. Format: YYYY-MM-DD HH:MM
    - `conversation_link` string, url — A URL that can open the conversation in the provider's side
    - `attachments` object[] — The list of attachments available in the message
      - `id` string, required — The ID of the attachment
      - `type` string, required — The mime-type of the attachment
      - `name` string — The name of the attachment
      - `size` number — The size of the attachment
      - `url` string, required — A URL to the file
      - `preview_url` string — A URL to a preview picture of the file
      - `link_expires` boolean — If true, it will use the getMessageById endpoint for fetching updated attachment's urls. Find out more [here](https://pipedrive.readme.io/docs/implementing-messaging-app-extension)

## Other responses

- `400` — Bad Request

---

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