messages

React to message

Put the sender profile's own emoji reaction on one sent LinkedIn message, or take it back with remove true (acknowledge without replying). gtm-api drives the account's browser and spends its pace; a reaction the row already shows costs nothing (result.dispatched false). 409 conflict: message_not_reactable (not a sent LinkedIn message, or a Sales Navigator one), sender_unavailable; 402 on a hold; 429 gtm_busy with retry_after; 503 when gtm-api does not answer.

Contract:

  • MCP tool react_to_message, registry package mcp.unibox/messages, mount unibox.inbox.
  • Operation action, response envelope action.
  • Flags: none.
post/api/messages/{sid}/react

Request

  • Base URL
    https://beta.getsales.io/unibox/v1
  • Auth
    HTTP bearer and API key in header Team-SID

Path parameters

sidstring required

The message to react to: a sent or delivered LinkedIn message (kind linkedin_message or linkedin_inmail) with a provider_message_sid. A draft, a queued or failed row, a connection note or an email row answers 409 message_not_reactable.

Request body

emojistring required

One emoji, "👍". LinkedIn's messenger takes any emoji; the quick set is 👍 ❤️ 👏 😂 😮 😢.

removeboolean

True takes the sender profile's own reaction with this emoji back instead of adding it. Explicit, never a toggle: read item.reactions[].is_viewer_reacted first and say which.

Response

action success envelope.

successtrue required
operation'action' required
actionstring required

kebab-case verb; matches the route segment.

Changes

No recorded changes to this operation across all 1 revision of this API.