Set the bot's reaction on a Telegram message

Sets the bot's emoji reaction on a Telegram message you sent or received, by messageId.

Endpoint

POST https://api.dairo.app/v1/messages/{messageId}/react

Sets the bot's emoji reaction on a Telegram message you sent or received, by messageId. emoji is required and must be one of Telegram's allowed reaction emoji — a custom or premium emoji returns 400. Set big: true to play the large-reaction animation. The target must be an outbound or inbound Telegram message you own; any other id returns 404. Requires the messages:send scope.

Scope: messages:send. Send the API key as a bearer token; Scopes lists what each one reaches.

Request

cURL

curl -X POST "https://api.dairo.app/v1/messages/3fa85f64-5717-4562-b3fc-2c963f66afa6/react" \
  -H "Authorization: Bearer $DAIRO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "emoji": "string"
  }'

Path parameters

Name	Type	Required	Description
`messageId`	string	yes	The Dairo message id (a telegram send or received message) to react to.

Body

Required, application/json: ReactTelegramMessageRequest.

Set the bot's emoji reaction on a Telegram message.

Field	Type	Required	Description
`emoji`	string	yes	A single Telegram-allowed reaction emoji (e.g. 👍 👎 ❤ 🔥).
`big`	boolean	no	Play the big-reaction animation. (default `false`)

Response

200 Success. Body: application/json, MessageActionResponse.

Field	Type	Required	Description
`object`	string	no
`id`	string	no	The message id acted on.
`channel`	string	no
`edited`	boolean	no
`editedAt`	string	no
`reacted`	boolean	no
`emoji`	string	no
`big`	boolean	no

200

{
  "object": "string",
  "id": "string",
  "channel": "string",
  "edited": true,
  "editedAt": "string",
  "reacted": true,
  "emoji": "string",
  "big": true
}

Errors

Every error has the same body, {"error": {"type", "code", "message", "param"}}; branch on code. Errors lists every code.

Status	Meaning
`400`	The request is malformed or a value is invalid (`invalid_request`, `invalid_domain`, `idempotency_key_mismatch`).
`401`	The API key is missing or invalid.
`403`	The key lacks the scope this endpoint needs (`scope_missing`) or may not do this (`not_permitted`).
`404`	No such resource in this account (`resource_not_found`).
`409`	The resource already exists or its state does not allow this (`duplicate_resource` or a condition-specific code).
`422`	The request is well-formed but a field failed validation (`validation_failed`).
`429`	Rate limit, plan limit, budget or spend cap reached (`rate_limited`, `plan_limit_reached`, `budget_exceeded`, `spend_cap_reached`).
`500`	An unexpected error; retry with backoff, then contact support (`internal_error`).