---
title: "PUT /v2/social/x/posts/{x_post_id}/reactions/{emoji}"
method: PUT
path: "/v2/social/x/posts/{x_post_id}/reactions/{emoji}"
tags: ["Social Community"]
deprecated: true
---

# PUT /v2/social/x/posts/{x_post_id}/reactions/{emoji}

`PUT /v2/social/x/posts/{x_post_id}/reactions/{emoji}`

## Request

- Base URL: `https://api.arbital.xyz` (the document declares no server; this is the origin it was published from)
- URL: `https://api.arbital.xyz/v2/social/x/posts/{x_post_id}/reactions/{emoji}`
- Auth: HTTP bearer

> **Deprecated.**

Idempotently add the authenticated viewer's emoji reaction to an X post that Indexer currently holds. Requires an unrestricted account. Only identity and Early interaction data are stored; X content is not copied. The first reaction pins the post against feed expiry; nothing is posted to X. Expired posts return 409 `x_post_expired`. Deprecated: use `POST /v2/social/reactions` with a `SocialReactionCommand` body.

## Path parameters

- `x_post_id` string, required
- `emoji` string, required

## Response `200`

Updated reaction summary

- SocialReactionSummary: CALLD reactions on one target, most used first. External-platform likes or counts are never merged in; source says so explicitly.
  - `reactions` SocialReactionCount[], required
    - `count` integer, required: Reactions with this emoji by active CALLD accounts.
    - `emoji` string, required
    - `viewer_reacted` boolean, required: Whether the signed-in viewer has this reaction; always false for anonymous readers.
  - `source` 'calld', required
  - `target` object, required
    - `id` string, uuid, required
    - `kind` 'post' | 'asset_comment' | 'thesis' | 'trade' | 'x_post', required

## Other responses

- `400`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `401`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `403`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `404`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `409`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `429`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.
- `503`: Stable machine-readable problem. HTTP 429 and 503 responses include retry and cache-validity fields plus Retry-After and X-Request-ID headers.

---

[API](https://skmtc.dev/arbital/apis/arbital-api.md) - [All operations](https://skmtc.dev/arbital/apis/arbital-api/llms.txt) - [OpenAPI document](https://skmtc.dev/arbital/apis/arbital-api/revisions/bb0185edf43a?raw)