System APIs
Update privilege details for the provided duty identifier and privilege identifier.
| HTTP method | PUT |
| URI | https://api.rambase.net/system/duties/{dutyId}/privileges/{privilegeId} |
| Supported formats | Xml, Html, Json (ex. $format=json) |
| - URI parameter {dutyId} |
Duty identifier
Integer, minimum 100000 |
| - URI parameter {privilegeId} |
Privilege identifier
Integer, minimum 100000 |
| Successful HTTP status code | 200 |
| API resource identifier | 2153, version 10 |
The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.
Privilege
This field is optional.
>DataRestriction
Datarestriction put on the link between a duty and a permission (privilege)
This field is optional.
>{String}</DataRestriction>RamBaseDataRestriction
The data restriction in RamBase internal syntax
This field is optional.
>{String}</RamBaseDataRestriction>Note
The group title field. Used to identify different mappings of the same permission that have different datarestrictions
This field is optional.
>{String}</Note>Privilege
This field is optional.
": {DataRestriction
Datarestriction put on the link between a duty and a permission (privilege)
This field is optional.
": "{String}",RamBaseDataRestriction
The data restriction in RamBase internal syntax
This field is optional.
": "{String}",Note
The group title field. Used to identify different mappings of the same permission that have different datarestrictions
This field is optional.
": "{String}"The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.
| $access_token String, optional | After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time. |
| $db String, optional | Set the database/company for the request |
| $useMinimumVersion Integer, optional | Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information. |
Read more about filters and sorting on how to use filter parameters and named filters.
Read more about filters and sorting on how to use sortable parameters
Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.
Please note that some fields may be removed from the response, based on user roles/duties/permissions.
List of available operations/actions for this resource.
See the operations documentation for more information about API operations.
Possible error codes the response might return:
| Error 101015 HTTP 404 | Permission not found |
| Error 101079 HTTP 400 | Mismatch in size of revision parameters |
| Error 107892 HTTP 403 | You don't have the requierd user level for this permission |
| Error 104493 HTTP 400 | Only JHC users can do global changes to privileges |
| Error 107890 HTTP 400 | Permission "{0}" has higher required user level than duty. |
| Error 101793 HTTP 400 | Permissions with no API reference can only be added to a specific duty once |