API

Collaboration APIs

POST collaboration/notebooks/{notebookId}/sections

Creates a new section in a notebook

HTTP method POST
URI https://api.rambase.net/collaboration/notebooks/{notebookId}/sections
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {notebookId} Notebook identifier
Integer, minimum 100000
Successful HTTP status code 201
API resource identifier 2617, version 4

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

Required/mandatory field

Name of a notebook section

>{String}</Name>
3
</Section>
1
{
2
     "section": {
3
          "name
Name

Required/mandatory field

Name of a notebook section

": "{String}"
4
     }
5
}

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
<Section>
2
     <SectionId
SectionId

Unique id reference to a section in a notebook

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

The status of a notebook section. 1= edit, 4 = main, 9 = obsolete

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

Name of a notebook section

>{String}</Name>
5
</Section>
1
{
2
     "section": {
3
          "sectionId
SectionId

Unique id reference to a section in a notebook

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

The status of a notebook section. 1= edit, 4 = main, 9 = obsolete

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

Name of a notebook section

": "{String}"
6
     }
7
}

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 101814 HTTP 404 Employee not found