API

RamBase REST APIs

GET system/roles/{roleId}/user-assignments/{userAssignmentId}

User assignment details for provided identifier

HTTP method GET
URI https://api.rambase.net/system/roles/{roleId}/user-assignments/{userAssignmentId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {roleId} Role identifier
Integer, minimum 100000
- URI parameter {userAssignmentId} User assignment identifier
Integer, minimum 1
Successful HTTP status code 200
API resource identifier 1931, version 15

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
<UserAssignment>
2
     <UserAssignmentId
UserAssignmentId

User assignment identifier

>{Integer}</UserAssignmentId>
3
     <Status
Status

Status for the user assignments

>{Integer}</Status>
4
     <ValidFrom
ValidFrom

Valid from date

>{Date}</ValidFrom>
5
     <ValidTo
ValidTo

Valid to date

>{Date}</ValidTo>
6
     <Comment
Comment

Description of why the user has been assigned to the role

>{String}</Comment>
7
     <Database
Database

Database the user has been assigned the role for

>{String}</Database>
8
     <User>
9
          <UserId
UserId

User identifier

>{Integer}</UserId>
10
          <FirstName
FirstName

First name of the user

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

>{String}</FirstName>
11
          <Name
Name

Name of the user

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

>{String}</Name>
12
          <UserLink
UserLink

User reference

>{String}</UserLink>
13
     </User>
14
</UserAssignment>
1
{
2
     "userAssignment": {
3
          "userAssignmentId
UserAssignmentId

User assignment identifier

": "{Integer}",
4
          "status
Status

Status for the user assignments

": "{Integer}",
5
          "validFrom
ValidFrom

Valid from date

": "{Date}",
6
          "validTo
ValidTo

Valid to date

": "{Date}",
7
          "comment
Comment

Description of why the user has been assigned to the role

": "{String}",
8
          "database
Database

Database the user has been assigned the role for

": "{String}",
9
          "user": {
10
               "userId
UserId

User identifier

": "{Integer}",
11
               "firstName
FirstName

First name of the user

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

": "{String}",
12
               "name
Name

Name of the user

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

": "{String}",
13
               "userLink
UserLink

User reference

": "{String}"
14
          }
15
     }
16
}

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 101053 HTTP 400 User assignment not found on this role