Skip to main content

[AirHost API] About API Usage

J
Written by Joelly See Toh
Updated today

Overview

AirHost provides an API for the purpose of linking with our own systems. This page explains how to start using it and access limitations.


Details

Usage Conditions:

Use of the API requires that you are subscribed to the AirHost ONE HMS Premium package, with a monthly license fee of at least 100,000 JPY.

API development is self-service. Our development team cannot provide development support, so please review the implementation overview and API documentation below and apply only if you determine that you can develop it yourself.

Note: The API only provides the features described in the API documentation . We cannot accommodate requests for additional features.


API License Types and Usage Fees

The API has two packages:

Package Name

Overview

Usage fee

Public API for PMS

This API allows you to obtain reservation information from the AirHost API and develop in-house systems that provide functions that AirHost PMS does not provide, such as accounting and cleaning management.

Basically, reservation information is read-only. It is not an API for creating a check-in app. If you would like to use advance check-in or self-check-in, please use the check-in option provided by AirHost.

5,000 yen + 100 yen/room

Booking Engine API

This is an API for developing your own booking engine (reservation site) by using the AirHost API to obtain inventory and price information.

5,000 yen + 100 yen/room

Pricing API

This is an API for retrieving and updating rate information in AirHost from external systems. It can be integrated with revenue management systems (RMS) or custom pricing logic to automatically update rates in AirHost.

※ This API is dedicated to rate updates only and does not support inventory updates or OTA-specific detailed controls.

5,000 yen + 100 yen/room

  • Each package requires an one time initial fee of 100,000 yen and a monthly fee for each API license. The initial fee includes the cost of providing a test environment and conducting acceptance tests.

  • Monthly fees for API licenses are not eligible for volume discounts.


Access Restrictions

The total number of accesses to all endpoints is limited to 20 times per minute. Please design your system so as not to exceed this limit.


Implementation method / API documentation

  1. How to implement the "Public API for PMS" package

  2. How to implement the "Booking Engine API" package

  3. How to implement the "Pricing API" package

How to Apply

If you are interested in using the service, please open the chat icon in the bottom left under your profile, click "Ask a question" to inquire about it, and select "Talk to a person." Send a message saying "I would like to use the API."

Conducting the "Acceptance Test"


After completing your implementation in the test environment, we will conduct an online acceptance test before granting access to the production environment.
During this test, you will be required to execute all interfaces that will be used in your application. AirHost will confirm proper operation using system logs on our end.


Room Type Change for Reservations

By specifying the room_type parameter in the Update a Room Reservation API, you can change the room type of an existing reservation.

When the room type is successfully updated, the following processes are automatically performed:

  • The inventory allocation for the original room type is released

  • The inventory for the new room type is newly allocated

Therefore, no manual inventory adjustment is required.

※ This feature applies only to reservations created via the API.


External System Integration

In general, API usage is intended for customers’ internal systems. Therefore, official integration or authorization with external cloud services (SaaS) is not provided.

However, it is acceptable for customers to use the API to retrieve data under their own responsibility, and then manage and process that data within their own systems before integrating it with external platforms.

Please note that the design, implementation, operation, and data management of any external system integration are entirely the responsibility of the customer.


Did this answer your question?