Migration API Fideltour V2 --> API HotelDataHub V1

Migration API Fideltour V2 --> API HotelDataHub V1

Autentification

In the old API, a TOKEN is provided to the provider and it uses it always adds in the header of all requests.

In the current API, a login request is required to obtain the TOKEN, which must then be added in the header of the rest of the requests.

The token expires at 24 hours and two methods are recommended to refresh it:

  • Refresh when receiving a 401,

  • Use check and token-refresh methods


Changes related to contacts

GET ahttps://backend.fideltour.com/api/3rd-party/contacts/

GET ahttps://app.hoteldatahub.io/api/v1/contacts/


Post ahttps://backend.fideltour.com/api/3rd-party/contacts/

Post ahttps://app.hoteldatahub.io/api/v1/contacts/


PATCH ahttps://backend.fideltour.com/api/3rd-party/contacts/

PATCH ahttps://app.hoteldatahub.io/api/v1/contacts/1234566/


  • The attribute "hc" should no longer be sent.

  • The attributes "first_name" and "last_name" have been replaced by "name" and "surname", respectively.

  • When performing a PATCH, it is necessary to include the contact ID in the url and it is not necessary to send your email in the body.


Changes related to reservations

GET ahttps://backend.fideltour.com/api/3rd-party/bookings/

GET ahttps://app.hoteldatahub.io/api/v1/entries/


Post ahttps://backend.fideltour.com/api/3rd-party/bookings/

Post ahttps://app.hoteldatahub.io/api/v1/entries/


PATCH ahttps://backend.fideltour.com/api/3rd-party/bookings/123455/

PATCH ahttps://app.hoteldatahub.io/api/v1/entries/123455/


  • The attribute "hc" has been replaced by "hotel_chain".

  • When creating a reservation, the contact attribute is mandatory, where the ID of the linked contact is sent.

  • The attributes "checkin" and "checkout" have been replaced by "entrance" and "departure", respectively.

  • In the "hotel" attribute must send the hotel ID(integer) provided by Fideltour.

  • The attributes "contact_first_name", "contact_last_name", "contact_email" and "contact_phone" are no longer used.

  • The following new attributes are added: "is_checkin_realized", "is_checkout_realized", "sub_status", "juniors", "room_number", "notes", "fare_type", "offer", "event_type", "package" and "category"


    • Related Articles

    • Introduction

      Getting started Introduction: In this article, we show how to consult and use the HotelDataHub/Fideltour API through the Swagger platform. There, we find the different endpoints (URLs) and the information that must be provided for each one to use the ...

    • Loyalty

      Loyalty Introduction: In this article we talk about API requests related to the Fideltour Loyalty module. The sections of the Swagger which include this information are: https://app.hoteldatahub.io/swagger/#/contacts ...

    • Booking management

      Table of contents: Introduction Use cases Methods available Table of parameters Examples: Petition (POST) Introduction: In this article we talk about API requests related to Bookings. Processing a booking: The endpoint is responsible for verifying ...

    • GDPR consent

      GDPR Consent Introduction: In this article, we talk about API requests related to the mandatory consents of the General Data Protection Regulation (GDPR in English), and how to manage it in our contacts. - Create consents for a contact - List and ...

    • Other connections

      Other Introduction In the Hotel Data Hub API, several numeric values are required, which serve to identify an item or element in Fideltour's database. We can deduce that if an item does not exist in the database, it must first be created in order to ...