API

System APIs

POST system/role-templates

Creates a new role template

HTTP method POST
URI https://api.rambase.net/system/role-templates
Supported formats Xml, Html, Json (ex. $format=json)
Successful HTTP status code 201
API resource identifier 6494, version 3

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
<RoleTemplate>
2
     <Name
Name

Required/mandatory field

Name of the role

>
{String}</Name>
3
     <RequiredUserLevel
RequiredUserLevel

The user level required to have this role. Only user having the same level or higher can be assigned.
This field also controls which duties can be added to the role. Only duties with the same level or lower can be added.

User levels (highest level first): Administrator, Partner, User, Portal user

Applicable domain values can be found here

Minimum value: 200

This field is optional.

>
{Integer}</RequiredUserLevel>
4
</RoleTemplate>
1
{
2
     "roleTemplate": {
3
          "name
Name

Required/mandatory field

Name of the role

":
"{String}",
4
          "requiredUserLevel
RequiredUserLevel

The user level required to have this role. Only user having the same level or higher can be assigned.
This field also controls which duties can be added to the role. Only duties with the same level or lower can be added.

User levels (highest level first): Administrator, Partner, User, Portal user

Applicable domain values can be found here

Minimum value: 200

This field is optional.

":
"{Integer}"
5
     }
6
}

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.

Format:
1
1

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 109048 HTTP 400 Role template with name {0} already exists
Error 109051 HTTP 403 The role template has duties with user level that is not allowed for the new user level specified on the role
Error 108042 HTTP 400 This required user level can only be assigned in development systems