Grant permissions
In this request, the auth-key
is the client that has permissions to modify Access Manager permissions, not the auth-key
you want to modify permissions on.
The one you are changing permissions for is within the parameters.
Path Parameters |
---|
sub_key string — REQUIREDYour app's subscribe key from Admin Portal. Example:
|
Query Parameters |
---|
signature string — REQUIREDUsed to verify the request was signed with the secret key associated with the subscribe key. For information on how to compute the signature, refer to Signature generation. Example:
|
auth string — REQUIREDThe Auth key that is being granted permissions. Example:
|
uuid stringA UTF-8 encoded string of up to 92 characters used to identify the client. Example:
|
timestamp integer — REQUIREDUnix epoch timestamp used as a nonce for signature computation. Must have no more than ± 60 second offset from NTP. This is not associated with the TTL at all. Example:
|
ttl integerTime to live for permission to be valid. Example:
|
channel stringThe channel name to perform the operation on. Comma separated values are accepted. Example:
|
channel-group stringComma-separated list of channel group names to perform the operation on. Example:
|
target-uuid stringSpecifies the channel groups on which to grant permissions. Comma separated values are accepted. Example:
|
w integerPossible values: [ Write permission Example:
|
r integerPossible values: [ Read permission |
m integerPossible values: [ Manage permission |
d integerPossible values: [ Delete permission |
g integerPossible values: [ Get permission |
u integerPossible values: [ Update permission |
j integerPossible values: [ Join permission |
Responses | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
200 OK
| |||||||||||||
400 Error validating inputs. (E.g. missing required params or invalid input types.) | |||||||||||||
403 Invalid signature. (E.g. wrong secret key or character set encoding for signature computation.) |