Finance APIs

POST finance/general-ledger

Resource for creating new general ledger posting

HTTP method	POST
URI	https://api.rambase.net/finance/general-ledger
Supported formats	Xml, Html, Json (ex. $format=json)
Custom fields	Custom fields supported
Successful HTTP status code	201
API resource identifier	5288, 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:

                                        <GeneralLedgerPosting>
                                    

<TransactionDate

TransactionDate

Required/mandatory field

Transaction date of general ledger posting

>{Date}</TransactionDate>

                                             <AccountingPeriod>
                                    

<Period

Period

Required/mandatory field

Accounting period

Minimum value: 190000

Maximum value: 290000

>{Integer}</Period>

                                             </AccountingPeriod>
                                    

<Category

Note

Remark of the general ledger posting

This field is optional.

>{String}</Note>

                                        </GeneralLedgerPosting>
                                    

{

                                             "generalLedgerPosting": {
                                    

"transactionDate

TransactionDate

Required/mandatory field

Transaction date of general ledger posting

": "{Date}",

                                                  "accountingPeriod": {
                                    

"period

Period

Required/mandatory field

Accounting period

Minimum value: 190000

Maximum value: 290000

": "{Integer}"

},

"category

Note

Remark of the general ledger posting

This field is optional.

": "{String}"

}

}

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]
$showCustomFields Boolean, optional	Set to "true" to include custom fields. Default value is false.

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:

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 101420 HTTP 404

Setting definition not found