curl --request GET \
--url https://api.partoo.co/v2/messages \
--header 'x-APIKey: <api-key>'{
"messages": [
{
"id": 123,
"conversation_id": 123,
"date": "2023-01-31 16:22:17.327878+00:00",
"content_type": "Text",
"sender_type": "User",
"sender_label": "Jane Doe",
"status": "Sending",
"is_deleted": false,
"content": "<string>",
"user_id": "<string>",
"custom_channel": "<unknown>"
}
],
"count": 1,
"next_cursor": "<string>"
}This endpoint lets you retrieve the messages for a specific conversation.
⚠️ This endpoint is paginated using cursor pagination. This means that in order to get the next page of results, you need to provide the cursor returned in the previous call.
curl --request GET \
--url https://api.partoo.co/v2/messages \
--header 'x-APIKey: <api-key>'{
"messages": [
{
"id": 123,
"conversation_id": 123,
"date": "2023-01-31 16:22:17.327878+00:00",
"content_type": "Text",
"sender_type": "User",
"sender_label": "Jane Doe",
"status": "Sending",
"is_deleted": false,
"content": "<string>",
"user_id": "<string>",
"custom_channel": "<unknown>"
}
],
"count": 1,
"next_cursor": "<string>"
}The authentication system on Partoo API is using API Key that should be put in the header of the request (the name of the header is x-APIKey). An api_key is linked to a user. This user's role will give you different access level to the API features.
The id of the conversation
Number of items to return per page.
1 <= x <= 100The cursor identifiying the page of data to fetch. If no cursor is provided, the query will return the first page of data. A cursor for the next page of data is provided in the response of this request.
OK
Response object
The list of messages for a specific conversation, paginated.
Show child attributes
The id of the message.
The id of the parent conversation.
The date at which the message was sent or received, in the ISO 8601 format (ex: "2023-01-31 16:22:17.327878+00:00").
"2023-01-31 16:22:17.327878+00:00"
The type of the message:
⚠️ New values may be added to this enum without prior notice and without following the classic depreciation cycle.
It is up to you to gracefully handle the case where new values are added.
We recommend showing a "Unhandled content" placeholder to the user in place of the message ⚠️
Text, Image, Video, Audio, Document, IgStoryReply, IgStoryMention, Unsupported Describes the person that sent the Message:
⚠️ New values may be added to this enum without prior notice and without following the classic depreciation cycle.
It is up to you to gracefully handle the case where new values are added.
We recommend ignoring messages with unhandled sender_type ⚠️
User, Consumer, Metadata Name of the person sending the message
"Jane Doe"
The delivery status of the message. Messages send via Partoo are created with the status "Sending", and propagated to the messaging channel. If the message is sent successfully, the status is changed to "Success". If the messaging channel fails to send the message, the status changed to "Failed". A failed message can be retried using the /retry endpoint.
Sending, Success, Failed If the message has been deleted by the consumer on the messaging channel (for now, only "Instagram" messages can be deleted).
false
The text of the message.
For "User" messages sent via the Partoo application, the id of the user that sent the message.
Total number of results available for the filters and dimensions requested.
1
The cursor to use in order to retrieve the next page of data. When all data have been fetched, the value is null.
Was this page helpful?