How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Later Conversations API

The Conversations API from Later — 17 operation(s) for conversations.

Later Conversations API is one of 176 APIs that Later publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Conversations. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, authentication docs, and pricing.

This API exposes 18 operations across 17 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: http://app.splashscore.com/v1, https://app.splashscore.com/v1.

18 operations 17 paths 23 schemas 1 DELETE8 GET7 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://app.later.com/
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Later Conversations API declares 1 security scheme for authenticating requests. An API key is passed in the header as api-key (apiKey). By default, every request must be authenticated.

Paths & Operations 18

Across 17 paths, the API surfaces 18 operations — 1 DELETE, 8 GET, 7 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Conversations 18
GET
/conversations/general-folders
Get the General Folders Unread Counts.
getGeneralFolders 1 param → 200400401403404500
GET
/conversations/dynamic-campaign-folders
Get the General Folders Unread Counts.
getCampaignFolders 3 params → 200400401403404500
GET
/messages/{id}
Retrieve a message by id.
getMessage 2 params → 200400401403500
POST
/draft
Send a new message.
createDraft 2 params → 200400401403404500
PUT
/draft/{messageId}
Update the draft.
updateDraft 2 params → 200400401403404500
DELETE
/draft/{messageId}
Throw out the draft.
throwOutDraft 1 param → 200400401403404500
PUT
/sendMessage/{messageId}
Send a message.
sendMessage 1 param → 200400401403404500
POST
/messages/{messageId}/reply
Reply to a message.
replyToMessage 2 params → 200400401403404500
GET
/conversations
Retrieve conversations.
getConversations 7 params → 200400401403500
GET
/find-all-conversations
Retrieve conversations.
findAllConversations 7 params → 200400401403500
GET
/count-conversations
Retrieve conversations.
countConversations 7 params → 200400401403500
GET
/conversations/{id}
Retrieve a conversation by id.
getConversation 2 params → 200400401403404500
POST
/v1/conversations/bulk-action/read
bulkMarkConversationsAsRead body → 201422500
POST
/v1/conversations/bulk-action/unread
bulkMarkConversationsAsUnread body → 201422500
POST
/v1/conversations/bulk-action/archive
bulkArchiveConversations body → 201422500
POST
/v1/conversations/bulk-action/unarchive
bulkUnarchiveConversations body → 201422500
POST
/v1/inline-images
uploadInlineImage body → 200400403500
GET
/v1/messages/{messageId}/events
getMessageEvents 6 params → 200400403404500

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are InstanceUserMaterializedView (52 properties), Message (24 properties), Conversation (19 properties), ListMemberDeprecated (18 properties). Each schema is shown below with its type and property counts.

ServerError
object
2 properties 2 required
WorkflowStatusRequirementDeprecated
object
3 properties
CampaignFolder
object
3 properties
GeneralFolders
object
5 properties
Conversation
object
19 properties
ConversationTemplateDeprecated
object
17 properties
Message
object
24 properties
UploadInlineImageResult
object
1 property 1 required
MessageRecipient
object
4 properties
DBMessageEvent
object
10 properties 3 required
ConversationBulkActionRequestBody
object
2 properties
QueryByMessageResult
object
2 properties 2 required
Error
object
6 properties
NotFoundError
object
2 properties 2 required
ListMemberDeprecated
object
18 properties
ConversationResponseMetadata
object
4 properties
ListCustomStatusDeprecated
object
12 properties 1 required
Attachment
object
8 properties
ForbiddenError
object
2 properties 2 required
InstanceUserMaterializedView
object
52 properties
ValidateErrorJSON
object
2 properties 2 required
LinksDeprecated
object
2 properties
AdministratorDeprecated
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

later-conversations-api-openapi.yml Raw ↑

Other APIs Later publishes across the network.

Later Social Media Platform
Later Account Invitations API
Later Action Groups API
Later Action Group Brief API
Later Action Group Bulk Scheduled Messages API
Later Action Group Conversation Templates API
Later Action Group Custom Influencer Statuses API
Later Action Group Custom Statuses API
Later Action Groups API
Later Action Group Scheduled Messages API
Later Action Groups Status API
Later Actions API
Where this information came from

This is an independent, third-party profile of Later Conversations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.