API

System APIs

GET system/roles/{roleId}/duties/{dutyId}

User assignment details for provided identifier

HTTP method GET
URI https://api.rambase.net/system/roles/{roleId}/duties/{dutyId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {roleId} Role identifier
Integer, minimum 100000
- URI parameter {dutyId} Duty identifier
Integer, minimum 1
Successful HTTP status code 200
API resource identifier 2167, version 11

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.

Format:
1
1

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.

$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]
$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
$format String, optional Set the format of the response to use for the request. Accepted values are "xml", "html", "jsonstream", "json"
$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.
$select String, optional Use to define the fields to return in the response. Accepts a comma-separated list of field names. See the Expand and select page for more information.
$expand String, optional Use to include output fields that are not returned by default in the response. Accepts a comma-separated list of expandable field names. See the Expand and Select 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.

Format:
1
<Duty>
2
     <DutyId
DutyId

Duty identifier

>
{Integer}</DutyId>
3
     <Name
Name

Name of the duty

>
{String}</Name>
4
     <TranslatedName
TranslatedName

Name translated to selected language. If no translation exists for the given langauage, english name will show.

This field is greyed out because it is an expandable field. You have to add $expand=TranslatedName in your request URI to get this field

>
{String}</TranslatedName>
5
     <Description
Description

Description of the duty

>
{String}</Description>
6
     <TranslatedDescription
TranslatedDescription

Description translated to selected language. If no translation exists for the given langauage, english description will show.

This field is greyed out because it is an expandable field. You have to add $expand=TranslatedDescription in your request URI to get this field

>
{String}</TranslatedDescription>
7
     <SubModule>
8
          <SubModuleId
SubModuleId

Submodule identifier

>
{Integer}</SubModuleId>
9
          <Name
Name

Name of the sub-module

>
{String}</Name>
10
          <TranslatedName
TranslatedName

Translated name of the submodule. The language used is specified either in $lang or by user settings. If translated name doesn't exist in desired language, english will be used.

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.TranslatedName in your request URI to get this field

>
{String}</TranslatedName>
11
          <Module
Module

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.Module in your request URI to get this field

>
12
               <ModuleId
ModuleId

Module identifier

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.Module in your request URI to get this field

>
{Integer}</ModuleId>
13
               <Name
Name

Name of the module

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.Module in your request URI to get this field

>
{String}</Name>
14
               <TranslatedName
TranslatedName

Translated name of the module. The language used is specified either in $lang or by user settings. If translated name doesn't exist in desired language, english will be used.

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.Module in your request URI to get this field

>
{String}</TranslatedName>
15
               <ModuleLink
ModuleLink

Module reference

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.Module in your request URI to get this field

>
{String}</ModuleLink>
16
          </Module>
17
          <SubModuleLink
SubModuleLink

Submodule reference

>
{String}</SubModuleLink>
18
     </SubModule>
19
     <DutyLink
DutyLink

Duty reference

>
{String}</DutyLink>
20
</Duty>
1
{
2
     "duty": {
3
          "dutyId
DutyId

Duty identifier

":
"{Integer}",
4
          "name
Name

Name of the duty

":
"{String}",
5
          "translatedName
TranslatedName

Name translated to selected language. If no translation exists for the given langauage, english name will show.

This field is greyed out because it is an expandable field. You have to add $expand=TranslatedName in your request URI to get this field

":
"{String}",
6
          "description
Description

Description of the duty

":
"{String}",
7
          "translatedDescription
TranslatedDescription

Description translated to selected language. If no translation exists for the given langauage, english description will show.

This field is greyed out because it is an expandable field. You have to add $expand=TranslatedDescription in your request URI to get this field

":
"{String}",
8
          "subModule": {
9
               "subModuleId
SubModuleId

Submodule identifier

":
"{Integer}",
10
               "name
Name

Name of the sub-module

":
"{String}",
11
               "translatedName
TranslatedName

Translated name of the submodule. The language used is specified either in $lang or by user settings. If translated name doesn't exist in desired language, english will be used.

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.TranslatedName in your request URI to get this field

":
"{String}",
12
               "module
Module

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.Module in your request URI to get this field

":
{
13
                    "moduleId
ModuleId

Module identifier

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.Module in your request URI to get this field

":
"{Integer}",
14
                    "name
Name

Name of the module

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.Module in your request URI to get this field

":
"{String}",
15
                    "translatedName
TranslatedName

Translated name of the module. The language used is specified either in $lang or by user settings. If translated name doesn't exist in desired language, english will be used.

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.Module in your request URI to get this field

":
"{String}",
16
                    "moduleLink
ModuleLink

Module reference

This field is greyed out because it is an expandable field. You have to add $expand=SubModule.Module in your request URI to get this field

":
"{String}"
17
               },
18
               "subModuleLink
SubModuleLink

Submodule reference

":
"{String}"
19
          },
20
          "dutyLink
DutyLink

Duty reference

":
"{String}"
21
     }
22
}

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 101013 HTTP 404 Sub-module not found