Inventory - API Example
This section describes the Inventory API. Get to know its Operations, Type Definitions, Default-Headers, and Default Query Parameters.
If you would like to see our other API modules, just select the relevant link:
API Reference | Description |
---|---|
Availability API | Allows you to manage room availability. |
Business Day API | Allows you to manage business day. |
Cashiering API | Allows you to manage cashiering. |
Configuration API | Allows you to read system configuration. |
Event Management API | Allows you to manage system events. |
Housekeeping API | Allows you to manage housekeeping work. |
Identity API | Allows you to manage user’s identity. |
Permission Management API | Allows you to manage system permissions. |
Profiles API | Allows you to create and manage individual, company, and travel agent profiles. |
Rate Manager API | Allows you to manage rate plans. |
Reporting API | Allows you to manage reports. |
Reservations API | Allows you to manage reservations. |
Authentication
Use this method to get a list of all available rooms.
Request parameters
The code of the type of the available room.
The date from which the room is available.
The date until which the room is available.
Request headers
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
Responses
The request was successful.
Body
Bad request. Response body contains error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
Internal Server Error.
Body
Authentication
Use this method to get a list of all available room types.
Request parameters
The date from which a specific room type is available.
The date until which a specific room type is available.
The code of the type of the available room type.
Request headers
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
Responses
The request was successful.
Body
Bad request. Response body contains error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
Internal server error.
Body
{id}
{id}
{id}
/updateAuthentication
Use this method to get a list of all house overbooking limits.
Request parameters
Filter the results based on a pattern.
Comma separated list of fields to sort the returned results.
Comma separated list of field names to be returned with a query operation.
The current page number when querying a list of resources.
Request headers
It is the unique identifier of the tenant/customer. The AC Project business perspective classifies the tenant as the AC customer.
If the method is calling out in the system administrator user context, an optional header parameter tenantID
determines the property of the organizational structure to which the tenant/customer belongs. In other cases, the context determines it.
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
Responses
The request was successful.
Request validation failed. Returned error-report contains validation error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
The requested resource has been not found
Internal server error
Body
Authentication
Use this method to create a new house overbooking limit.
Request headers
It is the unique identifier of the tenant/customer. The AC Project business perspective classifies the tenant as the AC customer.
If the method is calling out in the system administrator user context, an optional header parameter tenantID
determines the property of the organizational structure to which the tenant/customer belongs. In other cases, the context determines it.
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
Request body
Responses
The resource created successfully.
Headers
The URL of the created resource.
Body
Request validation failed. Returned error-report contains validation error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
The requested resource has been not found
Optimistic Concurrency error: request was passed with a version that is outdated
Body
Internal server error
Body
{id}
Authentication
Use this method to get the details of a specific house overbooking limit.
Path variables
The unique identifier of the house overbooking limit.
Request headers
It is the unique identifier of the tenant/customer. The AC Project business perspective classifies the tenant as the AC customer.
If the method is calling out in the system administrator user context, an optional header parameter tenantID
determines the property of the organizational structure to which the tenant/customer belongs. In other cases, the context determines it.
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
Responses
The request was successful.
Headers
Current version of Entity
Request validation failed. Returned error-report contains validation error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
The requested resource has been not found
Internal server error
Body
{id}
Authentication
Use this method to delete a specific house overbooking limit.
Path variables
The unique identifier of the house overbooking limit.
Request headers
It is the unique identifier of the tenant/customer. Tenant is the technichal concept in multi-tenant systems. From AC Project business perspective Tenant is the AC Customer
If the METHOD is called in system administator user context the optional header parameter tenantID defines the customer/tenant which organizational structure the property belongs to
If the method is called in customer user context, the context defines which customer/tenant organizatonal structure the property belongs to.
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
The method succeeds if the value of this subject header is identical with the value of the Etag received with the latest GET resource.
Responses
The server has fulfilled the request but does not need to return a message body.
Request validation failed. Returned error-report contains validation error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
The requested resource has been not found
Optimistic Concurrency error: request was passed with a version that is outdated
Body
Internal server error
Body
{id}
/updateAuthentication
Use this method to update a specific house overbooking limit.
Path variables
The unique identifier of the house overbooking limit.
Request headers
It is the unique identifier of the tenant/customer. Tenant is the technichal concept in multi-tenant systems. From AC Project business perspective Tenant is the AC Customer
If the METHOD is called in system administator user context the optional header parameter tenantID defines the customer/tenant which organizational structure the property belongs to
If the method is called in customer user context, the context defines which customer/tenant organizatonal structure the property belongs to.
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
The method succeeds if the value of this subject header is identical with the value of the Etag received with the latest GET resource.
Request body
Responses
The server has fulfilled the request but does not need to return a message body.
Request validation failed. Returned error-report contains validation error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
The requested resource has been not found
Optimistic Concurrency error: request was passed with a version that is outdated
Body
Internal server error
Body
{id}
{id}
{id}
/updateAuthentication
Use this method to get a list of overbooking limits for a specific room type.
Request parameters
Filter the results based on a pattern.
Comma separated list of fields to sort the returned results.
Comma separated list of field names to be returned with a query operation.
The current page number when querying a list of resources.
Request headers
It is the unique identifier of the tenant/customer. Tenant is the technichal concept in multi-tenant systems. From AC Project business perspective Tenant is the AC Customer
If the METHOD is called in system administator user context the optional header parameter tenantID defines the customer/tenant which organizational structure the property belongs to
If the method is called in customer user context, the context defines which customer/tenant organizatonal structure the property belongs to.
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
Responses
The request was successful.
Request validation failed. Returned error-report contains validation error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
The requested resource has been not found
Internal server error
Body
Authentication
Use this method to create a new overbooking limit for a specific room type.
Request headers
It is the unique identifier of the tenant/customer. Tenant is the technichal concept in multi-tenant systems. From AC Project business perspective Tenant is the AC Customer
If the METHOD is called in system administator user context the optional header parameter tenantID defines the customer/tenant which organizational structure the property belongs to
If the method is called in customer user context, the context defines which customer/tenant organizatonal structure the property belongs to.
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
Request body
Responses
The resource created successfully.
Headers
The URL of the created resource.
Body
Request validation failed. Returned error-report contains validation error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
The requested resource has been not found
Optimistic Concurrency error: request was passed with a version that is outdated
Body
Internal server error
Body
{id}
Authentication
Use this method to get the details of the overbooking limit for a specific room type.
Path variables
The unique identifier of the room type overbooking limit.
Request headers
It is the unique identifier of the tenant/customer. Tenant is the technichal concept in multi-tenant systems. From AC Project business perspective Tenant is the AC Customer
If the METHOD is called in system administator user context the optional header parameter tenantID defines the customer/tenant which organizational structure the property belongs to
If the method is called in customer user context, the context defines which customer/tenant organizatonal structure the property belongs to.
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
Responses
The request was successful.
Headers
Current version of Entity
Request validation failed. Returned error-report contains validation error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
The requested resource has been not found
Internal server error
Body
{id}
Authentication
Use this method to delete the overbooking limit for a specific room type.
Path variables
The unique identifier of the room type overbooking limit.
Request headers
It is the unique identifier of the tenant/customer. Tenant is the technichal concept in multi-tenant systems. From AC Project business perspective Tenant is the AC Customer
If the METHOD is called in system administator user context the optional header parameter tenantID defines the customer/tenant which organizational structure the property belongs to
If the method is called in customer user context, the context defines which customer/tenant organizatonal structure the property belongs to.
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
The method succeeds if the value of this subject header is identical with the value of the Etag received with the latest GET resource.
Responses
The server has fulfilled the request but does not need to return a message body.
Request validation failed. Returned error-report contains validation error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
The requested resource has been not found
Optimistic Concurrency error: request was passed with a version that is outdated
Body
Internal server error
Body
{id}
/updateAuthentication
Use this method to update the overbooking limit for a specific room type.
Path variables
The unique identifier of the room type overbooking limit.
Request headers
It is the unique identifier of the tenant/customer. Tenant is the technichal concept in multi-tenant systems. From AC Project business perspective Tenant is the AC Customer
If the METHOD is called in system administator user context the optional header parameter tenantID defines the customer/tenant which organizational structure the property belongs to
If the method is called in customer user context, the context defines which customer/tenant organizatonal structure the property belongs to.
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
The method succeeds if the value of this subject header is identical with the value of the Etag received with the latest GET resource.
Request body
Responses
The server has fulfilled the request but does not need to return a message body.
Request validation failed. Returned error-report contains validation error details.
Body
User is not authenticated. Please login before requesting this operation.
Authorisation failed. User is not authorize to request the operation on the defined resourse
The requested resource has been not found
Optimistic Concurrency error: request was passed with a version that is outdated
Body
Internal server error
Body
The start date of the overbooking limit.
The end date of the overbooking limit.
The number of rooms of a specific type that can be overbooked within a given date period.
The unique identifier of the room type with the overbooking limit.
The start date of the overbooking limit.
The end date of the overbooking limit.
The number of rooms of a specific type that can be overbooked within a given date period.
The start date of the overbooking limit.
The end date of the overbooking limit.
The number of rooms of a specific type that can be overbooked within a given date period.
The list of overbooking limits on the requested page.
The requested page information.
The unique identifier of the overbooking limit.
The start date of the overbooking limit.
The end date of the overbooking limit.
The number of rooms of a specific type that can be overbooked within a given date period.
The current version of an object, used for concurrency handling.
The list of overbooking limits on the requested page.
The requested page information.
The unique identifier of the overbooking limit.
The unique identifier of the room type with the overbooking limit.
The start date of the overbooking limit.
The end date of the overbooking limit.
The number of rooms of a specific type that can be overbooked within a given date period.
The code of the available room type.
The number of available rooms.
The number of available rooms including the overbooking limit.
The code of the available room.
The date for which the daily room occupancy is calculated.
The number of available rooms.
The number of available rooms including the overbooking limit.
The number of occupied rooms.
The language code in which the content is written based on 2 char ISO 639-1 standard
The content written for a specific geographic area, in a specific language.
The code of the error.
A human-readable message describing what happened.
The unique identifier of the request that caused the error.
A list of error details.
The code of the error.
A human-readable message describing what happened.
Exception-related names and values.
The name of the field(s) with incorrect values in the input request.
The language code in which the content is written based on 2 char ISO 639-1 standard
The content written for a specific geographic area, in a specific language.
The total number of results for a specific query.
The current page of results for a specific query.
A link to the first page of results for a specific query.
A link to the previous page of results for a specific query.
A link to the next page of results for a specific query.
A link to the last page of results for a specific query.
It is the unique identifier of the tenant/customer. The AC Project business perspective classifies the tenant as the AC customer.
If the method is calling out in the system administrator user context, an optional header parameter tenantID
determines the property of the organizational structure to which the tenant/customer belongs. In other cases, the context determines it.
Property ID header requested for each call that access data or operations under a specific property. Operations in different areas such as Reservation Creation/Update are strictly performed within a property context. Every such operation needs to include also this header. Other operations such as setting up configurations for a tenant are not executed within a property context, but within the tenant (or system) context. The default value is used to identify ACDEMO1 which is a test property used to try the API. How to find a property id:
- Use GET /configuration/subsidiaries/views/organization-treeendpoint to get a list of each subsidiary and the count of it’s properties, for a given tenant.
- Use GET /configuration/properties?subsidiaryId=<sub_id> to get a list of properties for the given subsidiary. Each entry will also contain a property Id.
The resource version returned from the server when the resource is accessed.
The method succeeds if the value of this subject header is identical with the value of the Etag received with the latest GET resource.
Authorization token.
Filter the results based on a pattern.
Comma separated list of fields to sort the returned results.
Comma separated list of field names to be returned with a query operation.
The current page number when querying a list of resources.
The maximum number of items to return with the current request.