Implementation plan for setting up as a generic OTA

Develper issues when using the Beds24 APi.
Post Reply
developer_villafinder
Posts: 9
Joined: Fri Mar 15, 2024 7:35 am

Hi,

Would you kindly advise on the implementation plan for setting ourselves up as a generic OTA?

Should we use this https://wiki.beds24.com/index.php/API_V2.0 or should we use this https://wiki.beds24.com/index.php/OTA?


Thanks and regards,
Ruoling
sorenjensen
Posts: 2
Joined: Mon Nov 06, 2023 2:24 pm

Hi Ruoling

I'd recommend using this https://wiki.beds24.com/index.php/OTA to set you up as a generic OTA.

If you have any questions regarding those functions, please feel free to write here in the forum or start a support ticket and we'll get back to you as soon as possible.

Best regards

Soren
developer_villafinder
Posts: 9
Joined: Fri Mar 15, 2024 7:35 am

Hi,

Oh dear. We have already done a lot of work on the OTA v2 API. What is the difference between the 2?

The Beds24 team pointed us to V2 to set up as a generic OTA.
" Your customers can connect to your channel via the generic OTA channel. We have a new API (API V2) which you can activate under SETTINGS > APPS & INTEGRATIONS > API The API documentation is available here: https://beds24.com/api/v2/ Additional documentation is available here: https://wiki.beds24.com/index.php/API_V2.0 "


Thank you,
Ruoling
developer_villafinder
Posts: 9
Joined: Fri Mar 15, 2024 7:35 am

Hi Sorsenjensen,

How would you advise for us to move forward from here? Now that we've already integrated with V2?

1. Would there be any upcoming upgrades on V2 to limiting access to bookings to only those that are created by 1 OTA?
2. Should we re-build our connection with V1? Would you have any suggestions on how to make the adaptation easier?


Thanks and regards,
Ruoling
sorenjensen
Posts: 2
Joined: Mon Nov 06, 2023 2:24 pm

Hi

1. There already is a feature for that, it's the https://beds24.com/api/v2/#/Bookings/get_bookings endpoint and you just have to specify the channel, then you'll be able to get the bookings for just one OTA at a time.

2. I wouldn't completely rebuild anything, since v1 and v2 is quite similar and offer the same things, we want to achieve parity between the two. If you hit any limits or restrictions that is possible to do in v1, then let us know and we'll see if we can add it to v2.

I hope that answers your questions, feel free to reach out to us again with any other questions you have.

Best regards

Soren
developer_villafinder
Posts: 9
Joined: Fri Mar 15, 2024 7:35 am

Hi,

Thank you for your advice.

In that case, we will implement https://beds24.com/api/v2/#/Bookings/get_bookings endpoint and specify the channel, to get the bookings for just one OTA at a time.

V2 Feature upgrade: the scope of each OTA should be limited to the bookings that are created by a specific OTA. Access to other bookings created by other OTAs is unnecessary for us and is of great concern to the property owners, which prevents them from completing the connection on V2 with us.

Please kindly keep up updated once this feature upgrade is completed. Would there any estimated timeline?


Best regards,
Ruoling
Post Reply