webhooks

Telegram Update

Receive one customer bot's updates.

Unauthenticated by necessity — Telegram delivers to a URL, not a session. Two independent checks stand in front: the signature in the path and the secret token Telegram echoes back in a header. Both run before any database work, and a failure never reveals whether the connection exists.

Anything past verification answers 200, even when it is ignored: Telegram retries non-2xx, and retrying a delivery that can never succeed is noise.

post/api/webhooks/telegram/{connection_id}/{signature}

Request

  • Base URL: https://api.heymetra.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.heymetra.com/api/webhooks/telegram/{connection_id}/{signature}
  • Auth: none declared

Path parameters

connection_idstring required
signaturestring required

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 5 revisions of this API.