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

Ando Messages API

Message and conversation message routes.

Ando Messages API is one of 8 APIs that Ando publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Message. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 4 operations across 3 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.ando.so/v1.

4 operations 3 paths 13 schemas 3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.ando.so/v1
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Ando Messages API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (AndoApiKey). It accepts HTTP bearer tokens (ando_sk) (BearerApiKey).

  • AndoApiKey — Workspace API key. Current accepted keys use the andosk prefix.
  • BearerApiKey — Compatibility transport for workspace API keys.

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Messages 4

Message and conversation message routes.

GET
/conversation-messages/{messageId}
Get a message
getConversationMessage 1 param → 200400401403404409429500
GET
/conversation-messages/{messageId}/replies
List thread replies
listThreadReplies 3 params → 200400401403404409429500
GET
/conversations/{conversationId}/messages
List conversation messages
listConversationMessages 3 params → 200400401403404409429500
POST
/conversations/{conversationId}/messages
Create a conversation message
createConversationMessage 2 params body → 200400401403404409429500

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are MessageResultResponse (12 properties), CreateConversationMessageBody (11 properties), MessageResult (11 properties), PublicApiPageInfo (6 properties). Each schema is shown below with its type and property counts.

ThreadRepliesData
object
Standard thread replies payload. Use threadrootid here to validate thread grouping; individual MessageResult items intentionally omit threadrootid and repliedt…
5 properties 5 required
ConversationMessagesData
object
Standard conversation messages payload.
4 properties 4 required
CreateConversationMessageBody
object
Create a conversation message. The authenticated API-key workspace member is the author; authorid is accepted only for legacy body compatibility and is ignored.
11 properties 1 required
LegacyErrorResponse
object
Current compatibility error envelope used by legacy /api/v1 routes.
3 properties 1 required
CreateConversationMessageResponse
object
Create-message response with the standard public data envelope plus legacy compatibility aliases.
3 properties 2 required
MessageResult
object
Public message result. This intentionally omits reply lineage fields such as threadrootid and repliedtomessageid; use the thread replies route and its threadro…
11 properties 11 required
MessageResultResponse
object
Message detail response with the standard public data envelope plus legacy top-level aliases.
12 properties 12 required
PublicApiPageInfo
object
Target public API pagination metadata with snakecase field names.
6 properties 1 required
LegacyPageInfo
object
Current compatibility pagination metadata with camelCase field names.
4 properties 2 required
ThreadRepliesResponse
object
Thread replies response with the standard public data envelope plus legacy top-level aliases. The response-level threadrootid identifies the requested root; in…
6 properties 6 required
PublicApiErrorResponse
object
Target public API error envelope.
1 property 1 required
ConversationMessagesResponse
object
Conversation messages response with the standard public data envelope plus legacy top-level aliases.
5 properties 5 required
MessageReactionSummary
object
Emoji reaction count for a message.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ando-messages-api-openapi.yml Raw ↑

Other APIs Ando publishes across the network.

Ando Calls API
Ando Clipboards API
Ando Members API
Ando Realtime API
Ando Search API
Ando Tasks API
Ando Webhooks API
Where this information came from

This is an independent, third-party profile of Ando Messages 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.