System APIs
Updates a custom number series
HTTP method | PUT |
URI | https://api.rambase.net/system/custom-number-series/{customNumberSeriesId} |
Supported formats | Xml, Html, Json (ex. $format=json) |
- URI parameter {customNumberSeriesId} |
Unique identifier for a flexible number series
Integer, minimum 100000 |
Successful HTTP status code | 200 |
API resource identifier | 6133, 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.
CustomNumberSerie
This field is optional.
>ObjectType
The document type like COA, CIN, ...
This field is optional.
>{String}</ObjectType>DocumentType
The sub document type like RENTAL, PRODUCTION, ...
This field is optional.
>{String}</DocumentType>ValidFrom
This is the data the number series should be running from
This field is optional.
>{Date}</ValidFrom>CustomNumberSerie
This field is optional.
": {ObjectType
The document type like COA, CIN, ...
This field is optional.
": "{String}",DocumentType
The sub document type like RENTAL, PRODUCTION, ...
This field is optional.
": "{String}",ValidFrom
This is the data the number series should be running from
This field is optional.
": "{Date}"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.
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 100138 HTTP 400 | Only the operators NE and EQ can be used on Values containing a comma list or wildcards ( ?, * ) |
Error 102063 HTTP 400 | Wildcard compare does not support both ? and * |
Error 102064 HTTP 400 | Wildcard compare does not support more than two asterisks (*) |