POST /conversations/messages/inbound
Post the necessary fields for the API to add a new inbound message.
Servers
- https://services.leadconnectorhq.com
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Version |
String | Yes |
API Version Valid values:
|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Authorization |
String | Yes |
Access Token |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
emailBcc[] |
Array | No |
List of email address to BCC |
emailFrom |
String | No |
From Email Address |
conversationProviderId |
String | Yes |
Conversation Provider Id |
conversationId |
String | Yes |
Conversation Id |
subject |
String | No |
Subject of the Email |
emailCc[] |
Array | No |
List of email address to CC |
date |
String | No |
Date of the inbound message |
altId |
String | No |
external mail provider's message id |
html |
String | No |
HTML Body of Email |
emailTo |
String | No |
To Email Address |
direction |
Object | No |
Message direction, if required can be set manually, default is outbound |
attachments[] |
Array | No |
Array of attachments |
message |
String | No |
Message Body |
type |
String | Yes |
Message Type Valid values:
|
emailMessageId |
String | No |
Send the email message id for which this email should be threaded. This is for replying to a specific email |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.