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

Entergram Messages API

Telegram message history and message write operations scoped to an explicit account and chat.

Entergram Messages API is one of 16 APIs that Entergram 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, authentication docs, and rate-limit docs.

This API exposes 12 operations across 8 paths, and defines 28 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against the base URL https://api.entergram.com.

12 operations 8 paths 28 schemas 1 DELETE4 GET1 PATCH4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.entergram.com
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

Entergram Messages API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Workspace-scoped PRO API key created in Entergram Settings Developers.

Paths & Operations 12

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

Messages 12

Telegram message history and message write operations scoped to an explicit account and chat.

GET
/v1/chats/{chat_id}/messages
List Telegram messages for a chat and account
list-chat-messages 5 params → 200400401403404422429500
POST
/v1/chats/{chat_id}/messages
Send a Telegram message
create-chat-message 1 param body → 201400401403404409422429
POST
/v1/chats/{chat_id}/messages/forward
Forward Telegram messages into a destination chat
forward-chat-messages 1 param body → 201400401403404409422429
POST
/v1/chats/{chat_id}/messages/media
Send uploaded Telegram media
create-chat-media-message 1 param body → 201400401403404409413422
POST
/v1/chats/{chat_id}/messages/media/uploads
Create upload tickets for Telegram media
create-chat-media-upload-tickets 1 param body → 201400401403404409413422
DELETE
/v1/chats/{chat_id}/messages/{message_id}
Delete a Telegram message
delete-chat-message 4 params → 204400401403404422429500
GET
/v1/chats/{chat_id}/messages/{message_id}
Get a single Telegram message
get-chat-message 4 params → 200400401403404422429500
PATCH
/v1/chats/{chat_id}/messages/{message_id}
Edit a Telegram message
update-chat-message 2 params body → 204400401403404409422429
GET
/v1/chats/{chat_id}/messages/{message_id}/media
Download Telegram message media
download-chat-message-media 4 params → 200206400401403404416422
GET
/v1/chats/{chat_id}/messages/{message_id}/reactions
Get detailed Telegram reactions for a message
get-chat-message-reactions 3 params → 200400401403404422429500
PUT
/v1/chats/{chat_id}/messages/{message_id}/reactions
Set your Telegram reactions on a message
set-chat-message-reactions 2 params body → 204400401403404409422429
PUT
/v1/messages/media/uploads/{upload_id}
Upload raw bytes for a reserved media ticket
upload-chat-media-bytes 5 params body → 200400401403404409413422

Schemas 28

The contract defines 28 schemas that model the data the API accepts and returns. The most detailed are Message (15 properties), HistoryMedia (8 properties), MediaUploadFileBody (7 properties), SendResult (6 properties). Each schema is shown below with its type and property counts.

SendResultEnvelope
object
1 property 1 required
CreateMediaMessageBody
object
6 properties 3 required
MessageReactionsEnvelope
object
1 property 1 required
HistoryEntity
object
5 properties
MessageReactionsResult
object
5 properties 3 required
SetMessageReactionsBody
object
2 properties 2 required
HistoryReaction
object
3 properties
ForwardMessagesBody
object
6 properties 3 required
MessageReaction
object
6 properties
MessagesPageEnvelope
object
1 property 1 required
HistoryPage
object
6 properties 4 required
SendResult
object
6 properties 1 required
UploadMediaResult
object
5 properties 5 required
MediaUploadTicketResult
object
3 properties 3 required
MediaUploadTicket
object
4 properties 4 required
HistoryMedia
object
8 properties
ReactionUser
object
4 properties
ErrorDetail
object
3 properties
MediaUploadEnvelope
object
1 property 1 required
UpdateMessageBody
object
3 properties 2 required
ErrorModel
object
6 properties
CreateMediaUploadTicketsBody
object
2 properties 2 required
CreateMessageBody
object
5 properties 3 required
Sender
object
3 properties
MediaUploadFileBody
object
7 properties 3 required
MessageEnvelope
object
1 property 1 required
Message
object
15 properties 3 required
MediaUploadTicketsEnvelope
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

entergram-messages-api-openapi.yml Raw ↑

Other APIs Entergram publishes across the network.

Entergram Accounts API
Entergram Chat Commands API
Entergram Chats API
Entergram Contacts API
Entergram Custom Fields API
Entergram Events API
Entergram Groups API
Entergram Live Chats API
Entergram Make webhooks API
Entergram Members API
Entergram System API
Entergram Tickets API
Where this information came from

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