Add action
Allows users to post action 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 sub_key, channel, timetoken), there is at most one unique (type, value) pair per UUID/userId.
There is a limit to the total number of actions which can be posted on a given message (default 25000).
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.
| Path Parameters | 
|---|
| sub_keystring —  REQUIREDYour app's subscribe key from Admin Portal. Example:
 | 
| channelstring —  REQUIREDThe channel ID to perform the operation on. Example:
 | 
| message_timetokenstring —  REQUIREDThe publish timetoken of a parent message. Example:
 | 
| Query Parameters | 
|---|
| authstringString which is either the auth key (Access Manager legacy) or a valid token (Access Manager) used to authorize the operation if access control is enabled. Example:
 | 
| uuidstring —  REQUIREDA UTF-8 encoded string of up to 92 characters used to identify the client. Example:
 | 
| signaturestringSignature 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. | 
| timestampintegerUnix 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. | 
|---|
| typestring | 
| valuestring | 
| Responses | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 200The message action was successfully added. 
 | |||||||||||||
| 207The message action was stored but failed to publish. 
 | |||||||||||||
| 400The post request contained invalid parameters. 
 | |||||||||||||
| 403The client isn't authorized to perform this operation. The authorization key you provided doesn't have the required permissions for this operation. 
 | |||||||||||||
| 409The action was already added 
 |