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

Unified.to messaging API

The messaging API from Unified.to — 5 operation(s) for messaging.

Unified.to messaging API is one of 140 APIs that Unified.to publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 13 JSON Schema definitions.

Tagged areas include Messaging. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 13 JSON Schemas.

This API exposes 10 operations across 5 paths, and defines 35 schemas. It is described by OpenAPI 3.0.0, at version 1.0.

Requests are made against 3 base URLs: https://api.unified.to, https://api-eu.unified.to, https://api-au.unified.to.

10 operations 5 paths 35 schemas 1 DELETE4 GET2 PATCH1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0
Servers
https://api.unified.to
https://api-eu.unified.to
https://api-au.unified.to
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Unified.to messaging API declares 1 security scheme for authenticating requests. An API key is passed in the header as authorization (jwt). By default, every request must be authenticated.

Paths & Operations 10

Across 5 paths, the API surfaces 10 operations — 1 DELETE, 4 GET, 2 PATCH, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

messaging 10
GET
/messaging/{connection_id}/channel
List All Channels
listMessagingChannels 11 params → 200
GET
/messaging/{connection_id}/channel/{id}
Retrieve a Channel
getMessagingChannel 4 params → 200
PATCH
/messaging/{connection_id}/event/{id}
Update an Event
patchMessagingEvent 4 params body → 200
PUT
/messaging/{connection_id}/event/{id}
Update an Event
updateMessagingEvent 4 params body → 200
GET
/messaging/{connection_id}/message
List All Messages
listMessagingMessages 17 params → 200
POST
/messaging/{connection_id}/message
Create a Message
createMessagingMessage 3 params body → 200
DELETE
/messaging/{connection_id}/message/{id}
Remove a Message
removeMessagingMessage 2 params → 200default
GET
/messaging/{connection_id}/message/{id}
Retrieve a Message
getMessagingMessage 4 params → 200
PATCH
/messaging/{connection_id}/message/{id}
Update a Message
patchMessagingMessage 4 params body → 200
PUT
/messaging/{connection_id}/message/{id}
Update a Message
updateMessagingMessage 4 params body → 200

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are property_MessagingEvent_message (25 properties), MessagingMessage (25 properties), MessagingChannel (12 properties), property_MessagingEvent_channel (12 properties). Each schema is shown below with its type and property counts.

property_MessagingMessage_mentioned_members
array
for email systems, this field represents the CC value
property_MessagingMessage_channels
array
Represents the names of all channels to which the message is sent. Identifies the channels where the message is posted.
property_MessagingEvent_message
object
25 properties
property_MessagingEvent_user
object
2 properties
property_MessagingEvent_message_channels
array
Represents the names of all channels to which the message is sent. Identifies the channels where the message is posted.
MessagingEvent
object
9 properties
property_MessagingEvent_message_destination_members
array
for email systems, this field represents the To value
MessagingMessages
array
property_MessagingEvent_message_mentioned_members
array
for email systems, this field represents the CC value
MessagingReference
object
2 properties
property_MessagingMessage_author_member
object
for email systems, this field represents the From value
4 properties
property_MessagingEvent_button
object
3 properties 1 required
property_MessagingMessage_attachments
array
property_MessagingMessage_channel_ids
array
@deprecated; use channels instead
property_MessagingEvent_message_buttons
array
property_MessagingMessage_reactions
array
property_MessagingMessage_destination_members
array
for email systems, this field represents the To value
property_MessagingChannel_members
array
MessagingMember
object
4 properties
property_MessagingMessage_hidden_members
array
for email systems, this field represents the BCC value
property_MessagingEvent_channel_members
array
property_MessagingEvent_message_hidden_members
array
for email systems, this field represents the BCC value
MessagingButton
object
3 properties 1 required
MessagingReaction
object
2 properties 2 required
property_MessagingEvent_message_author_member
object
for email systems, this field represents the From value
4 properties
property_MessagingEvent_message_attachments
array
MessagingChannels
array
MessagingChannel
object
12 properties 1 required
property_MessagingEvent_message_channel_ids
array
@deprecated; use channels instead
MessagingMessage
object
25 properties
MessagingAttachment
object
6 properties
property_MessagingEvent_message_reactions
array
property_MessagingEvent_channel
object
12 properties 1 required
property_MessagingMessage_buttons
array
property_MessagingReaction_member
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

unified-to-messaging-api-openapi.yml Raw ↑

Other APIs Unified.to publishes across the network.

Unified.to
Unified.to Authentication API
Unified.to account API
Unified.to accounting API
Unified.to activity API
Unified.to ad API
Unified.to ads API
Unified.to apicall API
Unified.to application API
Unified.to applicationstatus API
Unified.to assessment API
Unified.to ats API
Where this information came from

This is an independent, third-party profile of Unified.to messaging 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.