Skip to main content
POST
Send reaction

Authorizations

Authorization
string
header
required

Polymorfa organization key (pmfa_ prefix), project token (pmfa_pt_ prefix) where supported, or short-lived client token (pmfa_ct_ prefix). Organization and project keys may be personal or service-account owned and enforce selected action scopes. Organization keys cover the team and its projects; project tokens stay inside one project. Client tokens stay inside their live project and session and enforce their client rules.

Headers

Idempotency-Key
string

Unique key, 1 to 255 bytes of UTF-8, that makes this write safe to retry for 24 hours. A retry with the same key, credential, Polymorfa-Version, and request never runs the write again: it returns 409 idempotency_completed when the original succeeded, or the original server error, with Idempotent-Replayed: true. Reusing the key for a different request returns 409 idempotency_conflict; a retry while the original is still running returns 409 idempotency_in_progress, and a retry after an unrecorded outcome returns 409 idempotency_outcome_unknown.

Value constraints

Required string length: 1 - 255

Path Parameters

session
string
required

Identifier of the connected Polymorfa session.

Body

application/json
conversation
object
required

Public conversation identifier or E.164 phone number.

Accepted alternatives

id
string
required

Opaque Polymorfa resource ID. Keep this value as a string.

Value constraints

Pattern: ^[1-9][0-9]{0,18}$
Example:

"739182640518203"

reaction
string
required

Reaction applied to the referenced message.

Response

Reaction sent

success
enum<boolean>
required

Whether the request succeeded.

Allowed values

Available options:
true
data
object
required

Structured data carried by this object.