As part of the deployment of a Main Network Head (MNH), it is possible to set up a connector with the APIDAE SIT.
This can then be used to transform the "cold" records imported into the TDR into elloha accounts as follows: https: //elloha.zendesk.com/hc/fr/articles/360000833718-Comment-transformer-une-fiche-en-compte-elloha-
The service provider then takes control of his elloha account with most of the descriptive information already filled in, allowing him to concentrate on updating and pricing his offers and advertising his availability.
Important: A SIT connector is not intended to retrieve all the data you have in your SIT, but only the information that is useful for the elloha account. It is not a question of migrating your SIT to elloha. Some information is discarded because it is not useful in elloha. Other information is not imported because it is not essential or is too specific to certain slips (types of products) and the pro can always update his account directly in elloha.
In order to synchronise your APIDAE records in your Network Head, you need to create anExport/API type project in APIDAE.
This can be the same project you set up with your web agency to supply thewebsite.
Here is the technical configuration of the project to be set up:
Technologies used : API , Exports
Generation frequency: Daily
Include hidden objects: No
Format: JSON
Output format version: V2
Group exported objects: No
Export opening dates: Yes
Include source: No
A sample project:
The project must be shared with elloha so that your SIT records can be accessed and imported:
One or more Selections can be synchronised. You must create Selections dedicated to the connector with elloha.
You can create one for Accommodation and another for Activities depending on the needs of your elloha marketplace:
There is no need to place all the records in your SIT in these selections, just those that you want to transform into elloha accounts so that you can then hand over to your service provider:
Selections are imported every day of the week (Monday to Friday). This frequency implies that you place your SIT record in one of the synchronised Selections the day before and you will find it available for conversion the next day in your elloha Network Head.
If this is not the case, please check that it is in the Selection before contacting us via the Teamwork project space. If you need help setting up the Selections, contact your APIDAE advisor.
Once the project has been set up, to deploy the connector you must send us :
Theproject iD
The API Key
TheID or IDs of the selections to be synchronised
Once we have these elements, we will confirm that the connector has been set up.
Note thatas long as a file has not been transformed into an elloha account, it will be reimported on a daily basis. This ensures that the SIT records on the elloha side are kept up to date. If you update this file in elloha , your changes may be overwritten by the next import.
Toavoid this loss of data, you have two options:
- transform the form into an elloha account: ttps://elloha.zendesk.com/hc/en/articles/360000833718-How-to-transform-a-form-into-an-elloha-account
-remove the APIDAE record from the APIDAE Selection dedicated to elloha so that it is no longer synchronised
The SIT APIDAE connector automatically returns the idOI of elloha accounts from your transformed SIT records directly to the metadata in APIDAE.
This is described in detail in this article:
In this article you will find diagrams of the interactions between the elloha marketplace, your SIT and the websites created by your web agencies:
SIT file import mapping rules :
SIT record type APIDAE | Elloha file type TDR |
HOTELLERIE | HOTEL |
HOTEL_PLEIN_AIR | CAMPING |
ACTIVITY (Sports or other)* | SPORTS RECREATION |
ACTIVITY (Cultural activities)* | CULTURAL LEISURE |
TASTING | TASTING |
COLLECTIVE_ACCOMMODATION | RENTAL |
ACCOMMODATION_RENTAL** | RENTAL |
CULTURAL_HERITAGE | CULTURAL_HERITAGE |
NATURAL_HERITAGE | NATURAL HERITAGE |
RESTORATION | RESTAURANT |
COMMERCE_ET_SERVICE | not taken into account |
SKIABLE_AREA | not taken into account |
EQUIPMENT | not taken into account |
FESTIVAL_AND_EVENT | not taken into account |
HOLIDAY_PACKAGE | not taken into account |
STRUCTURE | not taken into account |
TERRITORY | not taken into account |
*Subtypes ACTIVITY:
Sports activities (activiteType.id=1789 or other): elloha SPORTS_LEISURE;
Cultural activities (activiteType.id=1790) : elloha LOISIR_CULTUREL;
**RENTAL sub-types:
Bed and Breakfast (hebergementLocatifType.id=2619) : elloha LOCATIF_SSTYPE_CHAMBRE_HOTES
Furnished accommodation and Gites (hebergementLocatifType.id=2620) : elloha LOCATIF_SSTYPE_MEUBLES_ET_GITES
Flat (hebergementLocatifType.id=2621) : elloha LOCATIF_SSTYPE_MEUBLES_ET_GITES
Chalet (hebergementLocatifType.id=2622) : elloha LOCATIF_SSTYPE_CHALET
Castles and prestigious residences (hebergementLocatifType.id=2623) : elloha LOCATIF_SSTYPE_RESIDENCES
House (hebergementLocatifType.id=2624) : elloha LOCATIF_RESIDENCE_TOURISME
HLL-chalet de loisirs, bungalow...(hebergementLocatifType.id=2625) : elloha LOCATIF_SSTYPE_CHALET
Unusual accommodation (hebergementLocatifType.id=2626) : elloha LOCATIF_SSTYPE_MEUBLES_ET_GITES