Telepath REST API Reference

Scope: telegram.read · Read-only action

Find a chat by name, username or numeric ID. This is not a global Telegram directory search.

Query parameters

Example request

curl 'https://telepath.lemma.company/api/v1/chats/search?query=Example&limit=10' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN"

HTTP 200 response

count and chats; search can include query. Chat entries include chat_id, name, type, username and archive coverage fields. Session reads add source, coverage and partial metadata.

{
  "count": 1,
  "chats": [
    {
      "chat_id": 123456789,
      "name": "Example contact",
      "type": "private",
      "username": null,
      "message_count": 1
    }
  ]
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

Search available message text. Optionally narrow to a chat and a lower date bound.

Query parameters

Example request

curl 'https://telepath.lemma.company/api/v1/messages/search?query=details&limit=20' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN"

HTTP 200 response

count and messages; single-chat reads include chat, search includes query, and date-filtered reads can include since. Message entries include chat_id, message_id, date, direction, text, text_source, sender and available media/transcript metadata.

{
  "count": 1,
  "messages": [
    {
      "chat_id": 123456789,
      "message_id": 42,
      "chat_name": "Example contact",
      "date": "2026-11-05T08:00:00.000Z",
      "direction": "incoming",
      "text": "Could you send the details?",
      "text_source": "written",
      "message_type": "text"
    }
  ]
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

Read a bounded message window in a chat. The REST gateway requires this chat to exist in the account archive before delegating a read.

Path: chat_id — required nonzero safe integer; chat must exist in this account archive.

Query parameters

Example request

curl 'https://telepath.lemma.company/api/v1/chats/123456789/messages?limit=20' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN"

HTTP 200 response

count and messages; single-chat reads include chat, search includes query, and date-filtered reads can include since. Message entries include chat_id, message_id, date, direction, text, text_source, sender and available media/transcript metadata.

{
  "count": 1,
  "messages": [
    {
      "chat_id": 123456789,
      "message_id": 42,
      "chat_name": "Example contact",
      "date": "2026-11-05T08:00:00.000Z",
      "direction": "incoming",
      "text": "Could you send the details?",
      "text_source": "written",
      "message_type": "text"
    }
  ]
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Send to a known private Business or group chat. Business replies require reply permission and an incoming message within the last 24 hours; groups send as the bot. Use channel post operations for channels. Ordinary sends have no idempotency key.

Path: chat_id — required nonzero safe integer; chat must exist in this account archive.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/chats/123456789/messages' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"text":"Thanks for your message."}'

HTTP 200 response

sent, chat_id, chat_name, message_id, date and text.

{
  "sent": true,
  "chat_id": 123456789,
  "chat_name": "Example contact",
  "message_id": 43,
  "date": "2026-11-05T08:01:00.000Z",
  "text": "Thanks for your message."
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

Retrieve up to five photos from one archived chat. Returns photo data and expiring links; n8n does not render the ChatGPT photo widget.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/messages/photos' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"chat_id":123456789,"message_ids":[42]}'

HTTP 200 response

count, bytes_per_photo and photos. Each entry has message_id and photo fields, or an error for that item; HTTP 200 does not mean every photo loaded.

{
  "count": 1,
  "bytes_per_photo": 250000,
  "photos": [
    {
      "message_id": 42,
      "data": "<base64 image bytes>",
      "mimeType": "image/jpeg",
      "bytes": 12345,
      "caption": null,
      "url": null
    }
  ]
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

List archived chats, including connected channels. An empty archive is not proof that Telegram has no messages.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/chats/list' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"limit":10}'

HTTP 200 response

count and chats; search can include query. Chat entries include chat_id, name, type, username and archive coverage fields. Session reads add source, coverage and partial metadata.

{
  "count": 1,
  "chats": [
    {
      "chat_id": 123456789,
      "name": "Example contact",
      "type": "private",
      "username": null,
      "message_count": 1
    }
  ]
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

Read recent saved messages across chats. New collection starts after Telegram connection; old history needs import.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/messages/recent' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"limit":20}'

HTTP 200 response

count and messages; single-chat reads include chat, search includes query, and date-filtered reads can include since. Message entries include chat_id, message_id, date, direction, text, text_source, sender and available media/transcript metadata.

{
  "count": 1,
  "messages": [
    {
      "chat_id": 123456789,
      "message_id": 42,
      "chat_name": "Example contact",
      "date": "2026-11-05T08:00:00.000Z",
      "direction": "incoming",
      "text": "Could you send the details?",
      "text_source": "written",
      "message_type": "text"
    }
  ]
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

Retrieve file metadata, an expiring link and extracted text when supported. Imported files without stored Telegram file IDs may be unavailable. Do not share download links with other users.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/messages/file' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"chat_id":123456789,"message_id":42,"include_text":true}'

HTTP 200 response

filename, mimeType, bytes, message_type, caption, expiring url and optional extracted text. Inspect text_error, text_truncated and line ranges; media in a text-only export may be unavailable.

{
  "filename": "example.txt",
  "mimeType": "text/plain",
  "bytes": 7,
  "message_type": "document",
  "caption": null,
  "url": null,
  "text": "Example",
  "text_truncated": false,
  "text_error": null
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

Return photo data and metadata through Telepath's existing media loader. Rendering or image understanding depends on the client; this is not an image-analysis endpoint.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/messages/photo' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"chat_id":123456789,"message_id":42}'

HTTP 200 response

Base64 data, mimeType, bytes, caption and an expiring url when available. This retrieves an image; it does not analyze it.

{
  "data": "<base64 image bytes>",
  "mimeType": "image/jpeg",
  "bytes": 12345,
  "caption": null,
  "url": null
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Confirm recipient and media before sending. Supply exactly one source: public HTTP(S) URL or from_chat_id plus from_message_id in your archive. Private messages use Business permissions; groups send as the bot. Never retry automatically after uncertain delivery.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/messages/send-media' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"chat_id":123456789,"url":"https://example.com/example.pdf","as_document":true}'

HTTP 200 response

sent, kind, chat_id, chat_name, message_id, filename, caption and sent_as. Delivery may be uncertain after a timeout.

{
  "sent": true,
  "kind": "document",
  "chat_id": 123456789,
  "chat_name": "Example contact",
  "message_id": 44,
  "filename": "example.pdf",
  "caption": null,
  "sent_as": "you"
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Confirm the exact replacement and recipient. Only eligible outgoing messages can be edited. Use dedicated post tools for channel posts.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/messages/edit' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"chat_id":123456789,"message_id":43,"text":"Updated reply."}'

HTTP 200 response

edited, chat_id, message_id and replacement text.

{
  "edited": true,
  "chat_id": 123456789,
  "message_id": 43,
  "text": "Updated reply."
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Mark a Business conversation read through Telegram, up to the given message or the newest known message. This changes the unread state; ordinary archive reads do not.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/messages/mark-read' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"chat_id":123456789,"message_id":42}'

HTTP 200 response

marked_read, chat_id, chat_name and up_to_message_id.

{
  "marked_read": true,
  "chat_id": 123456789,
  "chat_name": "Example contact",
  "up_to_message_id": 42
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Confirm the target and emoji. Reacts as the bot in supported groups or authorized connected channels; private Business reactions are unsupported. Omit emoji to remove the bot's reaction.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/messages/reaction' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"chat_id":-1001234567890,"message_id":42,"emoji":"👍"}'

HTTP 200 response

For a group: ok, chat_id, chat_name, message_id, reaction, removed and reacted_as. A channel result instead uses emoji and sent_as.

{
  "ok": true,
  "chat_id": -1001234567890,
  "chat_name": "Example group",
  "message_id": 42,
  "reaction": "👍",
  "removed": false,
  "reacted_as": "the bot"
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

Read the bot's separate direct-message inbox. Never mix this line with private Business chats, even when chat IDs match.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/bot/messages' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"limit":10}'

HTTP 200 response

count, note and messages. Entries use line=bot_dm, sender display name, date, text and also_has_business_chat. This inbox is separate from Business chats and channel DMs.

{
  "count": 1,
  "messages": [
    {
      "chat_id": 123456789,
      "message_id": 42,
      "from": "Example contact",
      "date": "2026-11-05T08:00:00.000Z",
      "text": "Hello",
      "line": "bot_dm",
      "also_has_business_chat": false
    }
  ]
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Send an authorized reply as the bot to someone present in this account's bot inbox. Does not reply in the owner's Business chat. Never automatically retry uncertain delivery.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/bot/reply' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"chat_id":123456789,"text":"Thanks for your message."}'

HTTP 200 response

ok, chat_id, sent_as and message_id.

{
  "ok": true,
  "chat_id": 123456789,
  "sent_as": "the bot",
  "message_id": 43
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Set a reaction as the bot on a message in this account's separate bot inbox. Omit emoji to remove the reaction.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/bot/reaction' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"chat_id":123456789,"message_id":42,"emoji":"👍"}'

HTTP 200 response

ok, chat_id, message_id, reaction, removed and reacted_as.

{
  "ok": true,
  "chat_id": 123456789,
  "message_id": 42,
  "reaction": "👍",
  "removed": false,
  "reacted_as": "the bot"
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Permanently delete Telepath archived messages in the specified scope. Does not delete messages in Telegram. Requires the account's archive deletion capability and explicit confirmation. Provide chat_id, before, or both.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/archive/forget' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"chat_id":123456789,"confirmed":true}'

HTTP 200 response

forgotten (row count), chat_id or null, before or null, and a note about retained copies. This removes archive data, not the Telegram conversation.

{
  "forgotten": 3,
  "chat_id": 123456789,
  "before": null,
  "note": "Removed from the archive. Telegram retains its copy."
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

Search this account's Notes. Empty query lists recent notes. Optionally filter by tag.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/notes/search' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"query":"Follow up","limit":10}'

HTTP 200 response

count and notes; search also includes query. List/search entries are note summaries, without full body, links or backlinks; use notes/get for those.

{
  "count": 1,
  "notes": [
    {
      "id": 17,
      "title": "Follow up",
      "type": "note",
      "tags": [],
      "task_status": null,
      "reminder": null,
      "created_at": "2026-11-05T08:00:00.000Z",
      "updated_at": "2026-11-05T08:00:00.000Z"
    }
  ]
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

Read one note, task, project or person with links and backlinks. Supply its ID or exact title.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/notes/get' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"id":17}'

HTTP 200 response

The note object: id, title, body, tags, type, task_status, reminder, created_at, updated_at, links and backlinks.

{
  "id": 17,
  "title": "Follow up",
  "body": "Send the requested details.",
  "tags": [],
  "type": "note",
  "task_status": null,
  "reminder": null,
  "created_at": "2026-11-05T08:00:00.000Z",
  "updated_at": "2026-11-05T08:00:00.000Z",
  "links": [],
  "backlinks": []
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

List recent notes, tasks and projects. Filter by tag when needed.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/notes/list' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"limit":10}'

HTTP 200 response

count and notes; search also includes query. List/search entries are note summaries, without full body, links or backlinks; use notes/get for those.

{
  "count": 1,
  "notes": [
    {
      "id": 17,
      "title": "Follow up",
      "type": "note",
      "tags": [],
      "task_status": null,
      "reminder": null,
      "created_at": "2026-11-05T08:00:00.000Z",
      "updated_at": "2026-11-05T08:00:00.000Z"
    }
  ]
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Save user-authorized content. Titles are unique; use [[Title]] links and tags. Types: note, project, person, task. Only explicitly authorized reminders on open tasks may be scheduled. A quota failure means the save did not happen. Search before creating duplicates.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/notes/create' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"title":"Follow up","body":"Send the requested details."}'

HTTP 200 response

The note object: id, title, body, tags, type, task_status, reminder, created_at, updated_at, links and backlinks.

{
  "id": 17,
  "title": "Follow up",
  "body": "Send the requested details.",
  "tags": [],
  "type": "note",
  "task_status": null,
  "reminder": null,
  "created_at": "2026-11-05T08:00:00.000Z",
  "updated_at": "2026-11-05T08:00:00.000Z",
  "links": [],
  "backlinks": []
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Read before editing. Use ID when renaming; otherwise title addresses the existing note. Omitted fields are preserved, append adds body text, tags replaces tags. reminder:null cancels; completing a task cancels its reminder. Confirm destructive replacements. Do not automatically retry append operations.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/notes/update' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"id":17,"body":"Updated details."}'

HTTP 200 response

The note object: id, title, body, tags, type, task_status, reminder, created_at, updated_at, links and backlinks.

{
  "id": 17,
  "title": "Follow up",
  "body": "Send the requested details.",
  "tags": [],
  "type": "note",
  "task_status": null,
  "reminder": null,
  "created_at": "2026-11-05T08:00:00.000Z",
  "updated_at": "2026-11-05T08:00:00.000Z",
  "links": [],
  "backlinks": []
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Permanently delete the chosen note after user confirmation. Also cancels its task reminder. Supply ID or exact title.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/notes/delete' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"id":17}'

HTTP 200 response

deleted, id and title.

{
  "deleted": true,
  "id": 17,
  "title": "Follow up"
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Schedule a one-time reminder only to the authenticated account owner. Clarify time, timezone and text; only schedule when authorized. Reuse request_id and identical details on retry. Creation allowance is shared with task reminders. Scheduled does not mean delivered.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/reminders/create' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"text":"Follow up","at":"2027-01-15T09:00:00Z","timezone":"Europe/London","request_id":"reminder-example-001"}'

HTTP 200 response

reminder, created and quota. An identical request_id replay returns created=false. Scheduled is not delivered.

{
  "reminder": {
    "id": "r_example_reminder",
    "kind": "standalone",
    "note_id": null,
    "at": "2027-01-15T09:00:00.000Z",
    "timezone": "Europe/London",
    "text": "Follow up",
    "status": "scheduled"
  },
  "created": true
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.read · Read-only action

List standalone/task reminders and delivery states. Available regardless of remaining creation allowance. By default excludes done/cancelled. Uncertain is not delivered.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/reminders/list' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"limit":10,"offset":0}'

HTTP 200 response

count, total, reminders, next_offset (or null) and quota. This endpoint supports offset pagination.

{
  "count": 1,
  "total": 1,
  "reminders": [
    {
      "id": "r_example_reminder",
      "kind": "standalone",
      "note_id": null,
      "at": "2027-01-15T09:00:00.000Z",
      "timezone": "Europe/London",
      "text": "Follow up",
      "status": "scheduled"
    }
  ],
  "next_offset": null
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Cancel by reminder ID at the owner's request; preserves linked task. Available even when Notes creation is disabled or allowance is exhausted. Cancellation does not restore creation allowance or recall an already sent message.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/reminders/cancel' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"id":"r_example_reminder"}'

HTTP 200 response

reminder and cancelled. Inspect the returned status; cancellation does not recall a delivered message.

{
  "reminder": {
    "id": "r_example_reminder",
    "kind": "standalone",
    "note_id": null,
    "at": "2027-01-15T09:00:00.000Z",
    "timezone": "Europe/London",
    "text": "Follow up",
    "status": "cancelled"
  },
  "cancelled": true
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Broadcast to a connected channel you currently own. Show channel, text, all media and button destinations and obtain explicit confirmation. Supports text, one photo/document, or 2–10 album items. Albums cannot have buttons or mix documents with photo/video. Captions max 1024. Requires bot Post messages permission. Reuse request_id for identical retries; never retry uncertain delivery with a new ID.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/channels/posts/create' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"channel_id":-1001234567890,"request_id":"post-create-example-001","confirmed":true,"text":"Example announcement."}'

HTTP 200 response

ok, channel_id, channel_title, message_id and action. Album creation also includes message_ids and media_group_id. Successful identical request_id replays return the saved result.

{
  "ok": true,
  "channel_id": -1001234567890,
  "channel_title": "Example channel",
  "message_id": 42,
  "action": "telegram_create_post"
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Read first, confirm channel and exact replacement. Omitted fields are preserved; empty buttons removes them. Requires current ownership and bot Edit messages permission. Targets one album item, not the whole album. Reuse request_id on identical retry.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/channels/posts/edit' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"channel_id":-1001234567890,"message_id":42,"request_id":"post-edit-example-001","confirmed":true,"text":"Updated announcement."}'

HTTP 200 response

ok, channel_id, channel_title, message_id and action. Album creation also includes message_ids and media_group_id. Successful identical request_id replays return the saved result.

{
  "ok": true,
  "channel_id": -1001234567890,
  "channel_title": "Example channel",
  "message_id": 42,
  "action": "telegram_edit_post"
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Permanently delete one archived post from Telegram after confirmation. Requires current ownership and bot Delete messages permission, subject to Telegram's deletion window. Not an archive-only delete. Reuse request_id on identical retry.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/channels/posts/delete' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"channel_id":-1001234567890,"message_id":42,"request_id":"post-delete-example-001","confirmed":true}'

HTTP 200 response

ok, channel_id, channel_title, message_id and action. Album creation also includes message_ids and media_group_id. Successful identical request_id replays return the saved result.

{
  "ok": true,
  "channel_id": -1001234567890,
  "channel_title": "Example channel",
  "message_id": 42,
  "action": "telegram_delete_post"
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.

Scope: telegram.write · Write action

Confirm the channel, post and desired state. Pin/unpin this specific post only; requires current ownership and bot Edit messages permission. Reuse request_id on identical retry.

JSON body

Example request

curl 'https://telepath.lemma.company/api/v1/channels/posts/pin' \
  -H "Authorization: Bearer $TELEPATH_ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"channel_id":-1001234567890,"message_id":42,"request_id":"post-pin-example-001","confirmed":true,"pinned":true}'

HTTP 200 response

ok, channel_id, channel_title, message_id and action. Album creation also includes message_ids and media_group_id. Successful identical request_id replays return the saved result.

{
  "ok": true,
  "channel_id": -1001234567890,
  "channel_title": "Example channel",
  "message_id": 42,
  "action": "telegram_set_post_pinned"
}

See shared errors and retry rules. Account permissions and feature availability are checked for every operation.