mirror of
https://github.com/tiennm99/miti-telegram.git
synced 2026-09-12 08:18:50 +00:00
tiennm99
76c04da6c4
Replace pnpm-lock.yaml with package-lock.json. pnpm-workspace.yaml's allowBuilds becomes package.json#allowScripts, which npm 11 gates the same way; sharp is omitted because it is no longer in the dependency tree.
MiTi-Telegram
A Cloudflare Worker that forward message to My Telegram
Usage
POST a JSON body to https://miti-telegram.miti99.workers.dev/ with a text field. Any other method returns 405; missing/empty text returns 400.
curl -X POST https://miti-telegram.miti99.workers.dev/ \
-H 'Content-Type: application/json' \
-d '{"text": "Hello from miti-telegram"}'
application/x-www-form-urlencoded (text=...) is also accepted. Responses are CORS-permissive (Access-Control-Allow-Origin: *).
The worker forwards text to Telegram as-is (no prepended metadata). For request enrichment (IP, UA, geo, etc.) use miti-loki instead.
For AI agents / Claude Code routines
Machine-readable usage spec: llms.txt, served at GET https://miti-telegram.miti99.workers.dev/llms.txt. It is the only GET route; every other GET returns 405, so no crawler or link preview can trigger a message.
Read this section first, do not probe.
- One POST per intended message. Do not send a
"test"payload to verify the endpoint — every successful POST forwards to Telegram, so probes spam the inbox. - Exact request:
POST https://miti-telegram.miti99.workers.dev/ Content-Type: application/json {"text": "<your message>"} - Success: any 2xx. Auth-related errors: 500 (worker missing
TELEGRAM_TOKEN/TELEGRAM_CHAT_IDenv vars — that's a deploy-time issue, not something a caller can fix). - Do not retry on 2xx. Each POST is a separate Telegram message; a retry would duplicate.