If the APIDAE connector is activated for your elloha Network Head, the APIDAE records transformed into elloha accounts will have their idOI automatically returned in the APIDAE metadata according to this process:
This function allows web service providers to automatically generate the elloha BE widget on the detail pages of the website as detailed in this article:
Let's take a look at the case of an elloha account containing several offers, such as several flats grouped together on an elloha Magic site or several guided tours managed in an elloha tourist information office account.
It is not possible to automatically link the offer id (productid) of one of the offers in an elloha account to APIDAE records, which are not elloha accounts but cold records, via the metadata.
elloha does not know which account offer should correspond to which APIDAE record.
In the specific case of cold APIDAE records that correspond to one of the offers in an elloha account, there are two ways of displaying the reservation on your website:
1-Manually enter the idOI/idOffer in APIDAE
If youenter the idOI (elloha account) and the productid (the offer for the account you are interested in) in the APIDAE record in your SIT, your web service provider will be able to rebuild a Booking-Engine widget (with an availability calendar) as on APIDAE records that correspond to an elloha account, which is generally the case for records that have metadata automatically entered in APIDAE.
Example:
To deploy this solution, the idOI and productid must be stored in APIDAE using the APIDAE metadata editor:
Here is an example of the metadata entered
Creation date 15/02/2021 Modification date 15/02/2021 Data { "id" : "7d2eb2a8-181b-42f7-9379-8afbeebf7e55", "productid" : "625b7212-5b20-4599-a15a-456a6f3f0331" }"id" => idOI of the elloha account
When you display the elloha account in your Network Header, it appears in the browser URL:
"productid" => offer or package id
Once the offer (accommodation accounts) or the package (activity accounts) is displayed in the elloha account, the productid appears in the address bar:
Note that you can use the catalogue reports of your elloha Network Head to extract the idOI and the offer or package id in Excel.
These reports are detailed in this article: Catalogue report which lists all the idOI of your elloha files and accounts.
If you are interested in the offer ids of elloha accommodations, please refer to section 3 - "All Offers" report for Accommodations accounts - Catalogue of offers with offer ids and generation of booking URLs
To list the Activities and their formulas: 4-Report "All Formulas" for Activity accounts - Catalogue of formulas with idFormula and generation of booking URLs
You also need to inform your web service provider that it must generate a BE elloha widget if the APIDAE record has the "Private description" field filled in, and not just if the metadata in the APIDAE record contains the idOI.
-If the web service provider finds the idOI in the record's metadata, it displays the widget pointing to the idOI (APIDAE record = elloha account). This is the general case.
-If it finds (idOI and productid) in the metadata, it displays the widget that points directly to the elloha account offer (case of 1 APIDAE record = 1 elloha account offer).
-If no metadata has been entered for the APIDAE record, nothing will be displayed for online booking.
2-You can also insert in the Booking block of the APIDAE form a URL type com medium containing the elloha booking-engine (BE) link pointing directly to the offer.
In this second case, the web service provider can "more simply" display a Book button that calls up the URL entered in the APIDAE cold file.
For example
Note:
If your APIDAE records are grouped together within a structure you can get the elloha account displayed there :
and at the bottom of the page, you will find cold files attached to the main file which offer a book button resulting from a direct entry in APIDAE. Tourist residences.
If you are planning to add a Book button (and not a BE widget with a calendar) to your website's records, you should opt for solution 2 for its simplicity.
-If the web service provider finds the idOI in the form's metadata, it will display a Book button pointing to the idOI (APIDAE form = elloha account).
-Otherwise, it displays a Book button that points to the Booking URL if the means of communication has been entered by the Tourism Office in APIDAE (APIDAE form/ 1 elloha account offer).
-If no metadata or booking URL has been entered, nothing is displayed for the booking.
Example of the generation of an elloha booking URL for an offer with
Les Bruyères
idoi=565feff1-160e-4aa9-b2f9-29e1608869b6
id APIDAE=5333887
In the elloha account, in the Modules menu, I create a Reservation Button widget:
I give it a name and select one of the offers in the account, then save it in the top right-hand corner:
I click on the Book button:
In the Browser tab that opens, you need to retrieve the URL:
https://reservation.elloha.com/?idPublication=39e859fc-6b99-4720-b71d-5b972be34754&idoi=565feff1-160e-4aa9-b2f9-29e1608869b6&idPrestation=bb5babfb-0230-4998-8d75-611cc525fdd3&culture=fr-FR&reload=1&searchFirstAvailableDates=1
In this URL, I still need to change the Publication ID to that of the Booking Engine (BE) of the Tourism Office, otherwise the sale will be attributed to the elloha account (direct sale via one of its modules) and not a sale by the Tourism Office Network Head.
For example, the general "dispo-resa" BE of the booking office is :
In the account booking link I replace the publication id to give :
https://reservation.elloha.com/?idPublication=9073ed7f-d5df-45f3-9920-237b90e09db0&idoi=565feff1-160e-4aa9-b2f9-29e1608869b6&idPrestation=bb5babfb-0230-4998-8d75-611cc525fdd3&culture=fr-FR&reload=1&searchFirstAvailableDates=1
This is the URL that must be entered in the APIDAE file "Les Bruyères / Appartement 4p - Rdj".
Note that creating a module for an elloha account is not compulsory. It allows you to retrieve the structure of a URL that points to an offer and the offerID that interests you.
If I have the idOI and the idPrestation (or idOffer it's the same) I can also build my booking URLs directly.