IMessages
v1 stable/IMessages/v1/
Send messages with text and files, and retrieve message history from channels.
Authentication required
All endpoints require Authorization: Bot <token> header.
Get a token →
/IMessages/v1/History ReadHistory Gets message history for a channel. Supports pagination via from (message ID) and limit (1–100, default 50).
Query Parameters
Response MessageHistoryResponse
Example
curl -X GET \
-H "Authorization: Bot YOUR_TOKEN" \
"https://gateway.argon.zone/IMessages/v1/History?channelId=...&from=...&limit=..." /IMessages/v1/Send SendMessages Sends a message to a channel. Include a unique randomId for deduplication; reply to another message via replyTo. attachments (at most 10, AttachFiles) are fileIds from IFiles/Upload with purpose attachment, or, in a multipart request with the same fields, parts, attach://<part> references or parts named attachments; the parts of one request share its 10 MiB limit. The response describes the attachments. Bots cannot post in announcement channels.
Request Body SendMessageRequest JSON or multipart/form-data
Send the body as JSON, or as multipart/form-data with the same fields —
each a text part, a list repeated once per value or given as one JSON array, and an object or a list of objects as its JSON.
In JSON a file is the fileId of an
IFiles/Upload; a form may also carry it as a part of the field's name
or as attach://<part>.
See Files & Attachments.
A file: the part of this name itself, or a text field holding attach://<name> (another part of the request) or the fileId of an IFiles/Upload.
Response SendMessageResponse
Errors
Example
curl -X POST \
-H "Authorization: Bot YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"channelId":"...","text":"...","randomId":"0","replyTo":null,"entities":null,"controls":null,"attachments":null}' \
https://gateway.argon.zone/IMessages/v1/Send