API

Rental APIs

GET rental/orders/{rentalOrderId}

Rental order details for provided identifier

HTTP method GET
URI https://api.rambase.net/rental/orders/{rentalOrderId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {rentalOrderId} Rental order identifier
Integer, minimum 100000
Successful HTTP status code 200
API resource identifier 2257, version 1

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.

$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
<RentalOrder>
2
     <RentalOrderId
RentalOrderId

Rental order identifier

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

Status of rental order

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

Reference to the sales order where an invoice plan was created

>
5
          <SalesOrderId
SalesOrderId

Sales order identifier

>{Integer}</SalesOrderId>
6
          <SalesOrderLink
SalesOrderLink

Sales order reference

>{String}</SalesOrderLink>
7
     </AdvanceInvoicePlanSource>
8
</RentalOrder>
1
{
2
     "rentalOrder": {
3
          "rentalOrderId
RentalOrderId

Rental order identifier

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

Status of rental order

": "{Integer}",
5
          "advanceInvoicePlanSource
AdvanceInvoicePlanSource

Reference to the sales order where an invoice plan was created

": {
6
               "salesOrderId
SalesOrderId

Sales order identifier

": "{Integer}",
7
               "salesOrderLink
SalesOrderLink

Sales order reference

": "{String}"
8
          }
9
     }
10
}

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 102738 HTTP 404 Price list not found
Error 100055 HTTP 403 You have only admittance to your own objects