---
title: "React to a WhatsApp message"
method: PUT
path: "/v1/whatsapp/messages/{message_id}/reaction"
tags: ["whatsapp-messages"]
---

# React to a WhatsApp message

`PUT /v1/whatsapp/messages/{message_id}/reaction`

## Request

- Base URL: `https://us1.platform.bird.com`
- URL: `https://us1.platform.bird.com/v1/whatsapp/messages/{message_id}/reaction`
- Auth: one of:
  - HTTP bearer
  - API key in cookie `bird_session`

Places an emoji reaction on a message this workspace received, the same way
tapping and holding a message in WhatsApp does.

You hold at most one reaction per message, so this replaces your existing
one rather than adding another. To take a reaction back entirely, delete it.

The `202` means the reaction was accepted, not that WhatsApp applied it.
Reactions carry no delivery or read receipt, so the furthest one gets is
sent. Read the message's `reactions` for what currently stands, or
[List reaction events for a WhatsApp message](/docs/api/reference/list-whatsapp-message-reaction-events)
for what became of each change, including one WhatsApp refused.

Each of these returns a `422`:

- A message this workspace sent. This endpoint places reactions on messages
  the contact sent; reacting to your own outbound message is not supported.
- More than one emoji, since WhatsApp takes exactly one.

A message Bird can no longer resolve returns a `404` instead. WhatsApp
accepts a reaction on a message up to 30 days old, but Bird keeps the
provider id a reaction needs for **15 days**, so that is the practical age
limit. The message and its reaction log stay readable for 30; only the id
a placement needs is gone.

Reacting to a message received in a group addresses the group, so the
group's own state applies: a group this workspace no longer holds returns
a `404` `WhatsAppGroupNotFound`, and one that is not active a `409`
`WhatsAppGroupNotActive`.

Reactions are not charged for.

## Path parameters

- `message_id` string, required

## Headers

- `Idempotency-Key` string
- `X-Workspace-Id` string
- `X-Organization-Id` string

## Request body

- WhatsAppReactionUpsert
  - `emoji` string, required: The emoji to place, as the character itself. Replaces your existing reaction on this message if you have one. To take a reaction back entirely, delete it rather than sending an empty value. WhatsApp takes exactly one emoji, so a value carrying more than one is refused with a `422` rather than sent. The length cap is generous because a single joined emoji is many code points: a couple-kissing one carrying two skin tones is ten, which is why the cap alone cannot express the limit.

## Response `202`

Reaction accepted; WhatsApp applies it asynchronously.

- WhatsAppReactionAccepted: A reaction as accepted, which WhatsApp has not applied yet and may still refuse. It names the reaction-log entry the request created, so a caller that places two changes on one message can tell which entry is which; read the message's `reactions` for what currently stands, or its reaction log for what became of this one.
  - `id` string, required
  - `emoji` string, required: The emoji as accepted, echoing the one the request carried.

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Insufficient permissions
- `404`: Resource not found
- `409`: Resource conflict
- `422`: The request has invalid field values, violates a business rule, or carries a query parameter the endpoint does not declare. Field validation errors use `type: validation_error` and include the affected fields in `details`. Business-rule errors identify the failed rule in `type`.
- `429`: Rate limit exceeded
- `500`: Internal server error
- `503`: The service is temporarily unavailable. If `Retry-After` is present, wait for that delay before retrying; otherwise, retry with exponential backoff. Reuse the same idempotency key and request when retrying a mutation.

---

[API](https://skmtc.dev/messagebird/apis/bird-api.md) · [All operations](https://skmtc.dev/messagebird/apis/bird-api/llms.txt) · [OpenAPI document](https://skmtc.dev/messagebird/apis/bird-api/revisions/3e2a50466454?raw)