API

Finance APIs

PUT finance/assets/{assetId}

Saves information about the finance asset

HTTP method PUT
URI https://api.rambase.net/finance/assets/{assetId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {assetId} Asset identifier
Integer, minimum 1
Successful HTTP status code 200
API resource identifier 3180, 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
<Asset
Asset

This field is optional.

>
2
     <Name
Name

Name of asset

This field is optional.

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

Description of finance asset

This field is optional.

>{String}</Description>
4
     <Validity
Validity

This field is optional.

>
5
          <EffectivePeriod
EffectivePeriod

Effective period of the finance asset

Minimum value: 199000

Maximum value: 299912

This field is optional.

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

Expiration period of the finance asset

Minimum value: 199000

Maximum value: 299912

This field is optional.

>{Integer}</ExpirationPeriod>
7
     </Validity>
8
</Asset>
1
{
2
     "asset
Asset

This field is optional.

": {
3
          "name
Name

Name of asset

This field is optional.

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

Description of finance asset

This field is optional.

": "{String}",
5
          "validity
Validity

This field is optional.

": {
6
               "effectivePeriod
EffectivePeriod

Effective period of the finance asset

Minimum value: 199000

Maximum value: 299912

This field is optional.

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

Expiration period of the finance asset

Minimum value: 199000

Maximum value: 299912

This field is optional.

": "{Integer}"
8
          }
9
     }
10
}

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.

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
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 101079 HTTP 400 Mismatch in size of revision parameters
Error 100613 HTTP 400 Expiration period must be later than effective period
Error 103701 HTTP 400 To period is not valid: {0}
Error 103703 HTTP 400 To period is not valid. General ledger postings exists.