API

Finance APIs

GET finance/departments/{departmentId}

Department details for the provided identifier

HTTP method GET
URI https://api.rambase.net/finance/departments/{departmentId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {departmentId} Department identifier
Integer, minimum 1
Successful HTTP status code 200
API resource identifier 420, version 12

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.

$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]
$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.

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
<Department>
2
     <DepartmentId
DepartmentId

Department identifier

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

Status of department

Possible domain values can be found here

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

Name of department

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

Description of department

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

Last general ledger posting period of department

>{Integer}</LastGeneralLedgerPostingPeriod>
7
     <CreatedAt
CreatedAt

Date and time of creation

>{Datetime}</CreatedAt>
8
     <CreatedBy>
9
          <EmployeeId
EmployeeId

Employee identifier

>{Integer}</EmployeeId>
10
          <LastName
LastName

Last name of employee

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

First name of employee

>{String}</FirstName>
12
          <EmployeeLink
EmployeeLink

Employee reference

>{String}</EmployeeLink>
13
     </CreatedBy>
14
     <Validity>
15
          <EffectivePeriod
EffectivePeriod

Effective period of the department

>{Integer}</EffectivePeriod>
16
          <ExpirationPeriod
ExpirationPeriod

Expiration period of the department

>{Integer}</ExpirationPeriod>
17
     </Validity>
18
     <Responsible>
19
          <EmployeeId
EmployeeId

Employee identifier

>{Integer}</EmployeeId>
20
          <LastName
LastName

Last name of employee

>{String}</LastName>
21
          <FirstName
FirstName

First name of employee

>{String}</FirstName>
22
          <EmployeeLink
EmployeeLink

Employee reference

>{String}</EmployeeLink>
23
     </Responsible>
24
</Department>
1
{
2
     "department": {
3
          "departmentId
DepartmentId

Department identifier

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

Status of department

Possible domain values can be found here

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

Name of department

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

Description of department

": "{String}",
7
          "lastGeneralLedgerPostingPeriod
LastGeneralLedgerPostingPeriod

Last general ledger posting period of department

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

Date and time of creation

": "{Datetime}",
9
          "createdBy": {
10
               "employeeId
EmployeeId

Employee identifier

": "{Integer}",
11
               "lastName
LastName

Last name of employee

": "{String}",
12
               "firstName
FirstName

First name of employee

": "{String}",
13
               "employeeLink
EmployeeLink

Employee reference

": "{String}"
14
          },
15
          "validity": {
16
               "effectivePeriod
EffectivePeriod

Effective period of the department

": "{Integer}",
17
               "expirationPeriod
ExpirationPeriod

Expiration period of the department

": "{Integer}"
18
          },
19
          "responsible": {
20
               "employeeId
EmployeeId

Employee identifier

": "{Integer}",
21
               "lastName
LastName

Last name of employee

": "{String}",
22
               "firstName
FirstName

First name of employee

": "{String}",
23
               "employeeLink
EmployeeLink

Employee reference

": "{String}"
24
          }
25
     }
26
}

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 100091 HTTP 404 Department not found