Zate

Free · Just Scan a QR Code

Te Zate Ree~

A free Telegram API for developers. Log in your Telegram account with a QR code, then send messages and stories and receive incoming ones over plain HTTP. Slow-grilled, served hot.

Get StartedAPI Reference
Try it now, no sign-up needed
$ curl -X POST https://api-zate.azickri.com/session
send-message.sh
$ curl -X POST https://api-zate.azickri.com/message \
    -H "id: $ZATE_ID" \
    -H "session-id: $ZATE_SESSION_ID" \
    -H "Content-Type: application/json" \
    -d '{
      "username": "@customer",
      "type": "text",
      "text": "Your OTP is 482913. Please keep it to yourself! 🔐"
    }'

200 OK { "messageId": "1024" }
Cak Zate fanning sate skewers at the Zate cart while the smoke flies off as Telegram paper planes

Cak Zate fanning the grill. The smoke? It flies straight off as Telegram messages. 🍢

The recipe

Three steps, done to perfection

Zate logs in to Telegram as a linked device, just like Telegram Desktop. The difference is that you drive it over HTTP.

  1. 1

    Create a session

    Get an id and a sessionId, the key to every other endpoint.

    POST/session
  2. 2

    Scan the QR

    Fetch the QR code and scan it from Settings → Devices → Link Desktop Device on your phone.

    GET/session
  3. 3

    Send anything

    Text, images, videos, audio, documents, locations, or contacts to usernames, users, groups, and channels.

    POST/message

API Reference

One serving, many skewers

One pair of headers is all it takes to open every Zate endpoint.

id+session-id

Session

6 endpoint
POST/sessionCreate a new sessionGET/sessionQR code and connection statusPOST/session/passwordTwo-step verification passwordPUT/session/webhookSet the incoming message webhookPUT/sessionReset and get a new QRDELETE/sessionDelete the session and its data

Send

3 endpoint
POST/messageMessage a user, group, or channelPOST/statusPost a text, image, or video storyPOST/typingShow "typing..."

Channel

3 endpoint
GET/channelChannels you followGET/channel/{id}One channel in detailGET/channel/messageChannel message history

Group

3 endpoint
GET/groupGroups you're inGET/group/{id}One group in detailGET/group/memberGroup member list

Why Zate?

No hassle from day one

Usually

  • Bots can only reply to people who pressed /start first
  • Handle MTProto, api_hash, and session strings yourself
  • Build your own listener, and lose messages while it is down
  • Telegram media has no public URL

With Zate

  • Use your own Telegram account and message users, groups, or channels
  • Scan a QR and you are done. Zate grills the MTProto for you
  • Webhooks with retries and automatic catch-up
  • Every media file gets a public link you can stream right away

Ready to order a serving?

Five minutes from now, your first message will land in Telegram. Rice cakes are optional, but recommended. 🍢

Start the Quick StartRead the ground rules first