Liveblocks Reactions API

The Reactions API from Liveblocks — 2 operation(s) for reactions.

Operations 2

POST /rooms/{roomId}/threads/{threadId}/comments/{commentId}/add-reaction Add reaction #
DELETE /rooms/{roomId}/threads/{threadId}/comments/{commentId}/remove-reaction Remove reaction #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/liveblocks-reactions-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

liveblocks-reactions-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Liveblocks REST Active Users Reactions API
  description: Server-side REST API for managing Liveblocks rooms, room storage, active users, broadcast events, comments and threads, Yjs documents, and version history. Authenticated with a secret key via HTTP Bearer authorization.
  version: v2
  contact:
    name: Liveblocks
    url: https://liveblocks.io/docs/api-reference/rest-api-endpoints
servers:
- url: https://api.liveblocks.io/v2
  description: Liveblocks REST API
security:
- bearerAuth: []
tags:
- name: Reactions
paths:
  /rooms/{roomId}/threads/{threadId}/comments/{commentId}/add-reaction:
    parameters:
    - $ref: '#/components/parameters/RoomId'
    - $ref: '#/components/parameters/ThreadId'
    - $ref: '#/components/parameters/CommentId'
    post:
      tags:
      - Reactions
      summary: Add reaction
      operationId: addReaction
      responses:
        '200':
          description: Reaction added.
  /rooms/{roomId}/threads/{threadId}/comments/{commentId}/remove-reaction:
    parameters:
    - $ref: '#/components/parameters/RoomId'
    - $ref: '#/components/parameters/ThreadId'
    - $ref: '#/components/parameters/CommentId'
    delete:
      tags:
      - Reactions
      summary: Remove reaction
      operationId: removeReaction
      responses:
        '204':
          description: Reaction removed.
components:
  parameters:
    ThreadId:
      name: threadId
      in: path
      required: true
      description: The thread identifier.
      schema:
        type: string
    CommentId:
      name: commentId
      in: path
      required: true
      description: The comment identifier.
      schema:
        type: string
    RoomId:
      name: roomId
      in: path
      required: true
      description: The room identifier.
      schema:
        type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: Authenticate with a Liveblocks secret key as a Bearer token.