New API Version — What Has Changed

New API Version — What Has Changed

We explain what has changed compared with the previous version and how this will help you to work with our product.

RateHawk Blog
4,0k
2 minutes read

Early check-in/Late check-out

Previously: in order to add one of these services to the order, you had to write to the account manager or support team.

Now: you can add early check-in/late check-out to the order directly when you make the booking.

Number of available rooms at a given rate

Previously: the number of available rooms at a given rate was not displayed.

Now: you can see how many rooms are left at the given rate.

Profile management

Previously: you could only add a new user in the online account on the site.

Now: you may add a new profile via the API and also view the full list of users, add, change, delete, activate, or deactivate any of the profiles.

Card payments

Previously: you could only pay for an order out of the credit limit.

Now: you may pay by card.

Launch in 14 languages

Previously: the API was only supported English.

Now: all languages found on Emerging Travel Group sites are now supported in the API — you may find information about hotels in Bulgarian, German, English, Spanish, French, Italian, Hungarian, Polish, Portuguese, Romanian, Russian, Serbian and Turkish.

Booking several rooms in a single order

Previously: in order to book more than one room (max 6), you had to create several orders.

Now: you may immediately select on the search page the required number of rooms and book them in a single order.

Reporting Documents

Previously: you could download the required documents only in the online account at RateHawk.

Now: all confirmatory accounting documents and vouchers may be downloaded via the API.

Canceling non-refundable bookings

Previously: bookings made at non-refundable rates could only be canceled on the site in the online account or via the support service.

Now: you may cancel non-refundable bookings directly via the API.

Updates to fields

Previously: outdated fields sometimes appeared randomly alongside current ones.

Now: only those fields containing up-to-date information have been retained.

New integration instructions

Previously: the instructions were in short form, and not all partners understood them entirely.

Now: we have described the entire integration process in detail in the new documents — now you won’t have a headache trying to figure out which method should follow which other one, meaning that integration will require less effort and time.

View the documents on the new version

Icon made by Gregor Cresnar from www.flaticon.com
Tags: product
Go to the top
4,0k
2 minutes read
Share with friends Share