API

Human resource APIs

POST human-resources/competencies/{competenceId}/role-expectations

Creates a new role expectation for provided competence

HTTP method POST
URI https://api.rambase.net/human-resources/competencies/{competenceId}/role-expectations
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {competenceId} Competence identifier
Integer, minimum 100000
Successful HTTP status code 201
API resource identifier 2994, version 5

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
<RoleExpectation>
2
     <ExpectedScore
ExpectedScore

Required/mandatory field

The score that is expected for this competence on this role

Applicable domain values can be found here

Minimum value: 0

Maximum value: 10

>
{Integer}</ExpectedScore>
3
     <Role>
4
          <RoleId
RoleId

Required/mandatory field

Role identifier

Minimum value: 100000

>
{Integer}</RoleId>
5
     </Role>
6
</RoleExpectation>
1
{
2
     "roleExpectation": {
3
          "expectedScore
ExpectedScore

Required/mandatory field

The score that is expected for this competence on this role

Applicable domain values can be found here

Minimum value: 0

Maximum value: 10

":
"{Integer}",
4
          "role": {
5
               "roleId
RoleId

Required/mandatory field

Role identifier

Minimum value: 100000

":
"{Integer}"
6
          }
7
     }
8
}

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.
$showDomainDescriptions Boolean, optional Set to "true" to include domain descriptions for fields using domain values. See the Domain values page for more information. Default value is false.
$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.

Format:
1
<RoleExpectation>
2
     <RoleExpectationId
RoleExpectationId

Role expectation identifier

>
{Integer}</RoleExpectationId>
3
     <CreatedAt
CreatedAt

Date and time of creation

>
{Datetime}</CreatedAt>
4
     <ExpectedScore
ExpectedScore

The score that is expected for this competence on this role

Possible domain values can be found here

>
{Integer}</ExpectedScore>
5
     <Role>
6
          <RoleId
RoleId

Role identifier

>
{Integer}</RoleId>
7
          <Name
Name

Name of the role

>
{String}</Name>
8
          <RoleLink
RoleLink

Role reference

>
{String}</RoleLink>
9
     </Role>
10
     <RoleExpectationLink
RoleExpectationLink

Competence role expectation link

>
{String}</RoleExpectationLink>
11
</RoleExpectation>
1
{
2
     "roleExpectation": {
3
          "roleExpectationId
RoleExpectationId

Role expectation identifier

":
"{Integer}",
4
          "createdAt
CreatedAt

Date and time of creation

":
"{Datetime}",
5
          "expectedScore
ExpectedScore

The score that is expected for this competence on this role

Possible domain values can be found here

":
"{Integer}",
6
          "role": {
7
               "roleId
RoleId

Role identifier

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

Name of the role

":
"{String}",
9
               "roleLink
RoleLink

Role reference

":
"{String}"
10
          },
11
          "roleExpectationLink
RoleExpectationLink

Competence role expectation link

":
"{String}"
12
     }
13
}

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 101606 HTTP 404 Module not found
Error 103562 HTTP 404 Role expectation for competence not found