Allows users to post actions on a parent message.
The server does not validate that the parent message exists at the time the action is posted. The server does, however, check that you have not already added this particular action to this message. In other words, for a given parent message (identified by
timetoken), there is at most one unique (
value) pair per UUID/userId.
There is a limit to the total number of actions which can be posted on a given message (default
If all goes well, the message action is stored in the database, and a specially structured
Action add event message is published in on the same channel as the parent message.
Your app's subscribe key from Admin Portal.
The channel name to perform the operation on.
The publish timetoken of a parent message.
String which is either the auth key (PAM v2) or a valid token (Access Manager) used to authorize the operation if access control is enabled.
Example: myAuth / p0thisAkFl043rhDdHRsCkNyZXisRGNoYW6hanNlY3JldAFDZ3Jwsample3KgQ3NwY6BDcGF0pERjaGFuoENnctokenVzcqBDc3BjoERtZXRhoENzaWdYIGOAeTyWGJI
A UTF-8 encoded string of up to 64 characters used to identify the client.
Signature used to verify that the request was signed with the secret key associated with the subscribe key.
If Access Manager is enabled, either a valid authorization token or a signature are required.
Check Access Manager documentation for details on how to compute the signature.
Unix epoch timestamp used as a nonce for signature computation. Must have no more than ± 60 seconds offset from NTP.
Required if the
|Request Body — REQUIRED|
JSON object with user properties.
The message action was successfully added.
The message action was stored but failed to publish.
The post request contained invalid parameters.
The client isn't authorized to perform this operation. The authorization key you provided doesn't have the required permissions for this operation.
The action was already added