RamBase REST APIs
Creates a new duty assignment for provided role.
| HTTP method | POST |
| URI | https://api.rambase.net/system/roles/{roleId}/duties |
| Supported formats | Xml, Html, Json (ex. $format=json) |
| - URI parameter {roleId} |
Role identifier
Integer, minimum 100000 |
| Successful HTTP status code | 201 |
| API resource identifier | 2166, version 7 |
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.
DutyId
Required/mandatory field
Duty identifier
Minimum value: 100000
>{Integer}</DutyId>DutyId
Required/mandatory field
Duty identifier
Minimum value: 100000
": "{Integer}"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. |
| $lang String, optional | Specifies the language used in the response, following the 3-letter ISO-639-1 [lll] |
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.
Please note that some fields may be removed from the response, based on user roles/duties/permissions.
DutyId
Duty identifier
>{Integer}</DutyId>Name
Name of the duty
>{String}</Name>Description
Description of the duty
>{String}</Description>SubModuleId
Submodule identifier
>{Integer}</SubModuleId>Name
Name of the sub-module
>ModuleId
Module identifier
>{Integer}</ModuleId>Name
Name of the module
>{String}</Name>ModuleLink
Module reference
>{String}</ModuleLink>SubModuleLink
Submodule reference
>{String}</SubModuleLink>DutyLink
Duty reference
>{String}</DutyLink>DutyId
Duty identifier
": "{Integer}",Name
Name of the duty
": "{String}",Description
Description of the duty
": "{String}",SubModuleId
Submodule identifier
": "{Integer}",Name
Name of the sub-module
": {ModuleId
Module identifier
": "{Integer}",Name
Name of the module
": "{String}",ModuleLink
Module reference
": "{String}"SubModuleLink
Submodule reference
": "{String}"DutyLink
Duty reference
": "{String}"
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 101420 HTTP 404 | Setting definition not found |
| Error 101824 HTTP 400 | The duty already exists on the role |
| Error 101827 HTTP 400 | Local duty can not be assigned to global role |