---
title: "Remove your reaction from a WhatsApp message"
method: DELETE
path: "/v1/whatsapp/messages/{message_id}/reaction"
tags: ["whatsapp-messages"]
---

# Remove your reaction from a WhatsApp message

`DELETE /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`

Takes back the reaction this workspace placed on a message, the same way
tapping your own reaction in WhatsApp does. Only your own reaction can be
removed; one the contact placed is theirs to take back.

Removing a reaction from a message you have not reacted to changes nothing
and still answers `202`, so a repeated call is safe.

A removal travels the same path as placing a reaction, so it is refused on
the same grounds. A message this workspace sent returns a `422`: it could
never have carried a reaction of ours to remove, since placing one there is
not supported either.

A message Bird can no longer resolve returns a `404` instead, on the same
15-day retention a placement is bounded by. A reaction on a message
received in a group addresses the group, so a group this workspace no
longer holds returns a `404` `WhatsAppGroupNotFound` and one that is not
active a `409` `WhatsAppGroupNotActive`, the same as placing one does.

The `202` is the removal accepted rather than applied. The reaction stays in
the message's `reactions` until WhatsApp confirms the removal and then drops
out, so one on its way off reads as still standing rather than disappearing
before it is gone.

## Path parameters

- `message_id` string, required

## Headers

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

## Response `202`

Removal accepted. No body: the reaction is still standing at this point, and on a message this workspace never reacted to there is nothing to return. Read the message's `reactions` to see it go.

## 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/6dfce1179799?raw)