---
title: "DELETE /v2/social/trades/{event_id}/reactions/{emoji}"
method: DELETE
path: "/v2/social/trades/{event_id}/reactions/{emoji}"
tags: ["Social Community"]
deprecated: true
---

# DELETE /v2/social/trades/{event_id}/reactions/{emoji}

`DELETE /v2/social/trades/{event_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/trades/{event_id}/reactions/{emoji}`
- Auth: HTTP bearer

> **Deprecated.**

Authenticated CALLD reactions on a stable local Fomo/Pump trade event UUID. Latest upsert and current external actor visibility are required (404 hidden, 503 unavailable). PUT and DELETE are idempotent. DELETE commits own removal before the optional visible summary, even after restriction or retraction. Deprecated: use `POST /v2/social/reactions` with a `SocialReactionCommand` body.

## Path parameters

- `event_id` string, uuid, 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.
- `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)