Pagination can be controlled using
limit parameters, where
start is not provided, the server uses the current time. Providing no
limit means there is no limit to the number of actions being requested. In this event the server will try and retrieve all actions for the channel, going back in time forever. In some cases, due to internal limitations on the number of queries performed per request, the server will not be able to give the full range of actions requested. In these cases a
more link will be provided. This is a signal that internal limiting has occurred, and the
more link itself can be used to continue fetching the originally requested range of actions.
Your app's subscribe key from Admin Portal.
The channel name to perform the operation on.
Action timetoken denoting the start of the range requested. Returned values will be less than
Action timetoken denoting the end of the range requested. Returned values will be greater than or equal to
Number of actions to return in response.
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
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
The actions were fetched.
The subscribe key is invalid.
The client isn't authorized to perform this operation.