Release | Create guidebook release
This article describes how to publish guidebook by connecting to another software. Software systems communicate with Application-Programming-Intefaces (API).
Last updated
This article describes how to publish guidebook by connecting to another software. Software systems communicate with Application-Programming-Intefaces (API).
Last updated
GUIBOs APIs are all REST services, exchanging JSON through HTTP
Prerequisite: You have created a travel plan with a unique ID. This ID is required to define the travel plan for which a release is to be created and should be known to the external system from which the download release is triggered.
Creation of the download permission can be done by calling our REST/https service. This example create downloadpermissions for two devices for the trip "234"
Replace CCCCCC with the customer ID, you can find this under Account Settings > General Settings > Account ID
Replace xxxxxx-xxxxxx-xxxxxx-xxxxxx with the API key, you can find this under Account Settings > General Settings > API Key
A release requires startdate and enddate, the period during which the guidebook can be downloaded and will be available in the App.
Optional, but recommended are arrivaldate and departuredate; these must fall within the specified startdate and enddate. Those dates enable the App to show specific content for each day during the journey.
Prerequisite:
You have previously created the content to be added to the itinerary in a library. In the following example, content from the libraries with the IDs "HOTELS" and "TEXTINFO" is used
In the following example, the hotel "Zur Post" with the external ID "HPO1" is added to the trip "234" for the customer with the booking number/download code "556678".
Replace CCCCCC with the customer ID, you can find this under Account Settings > General Settings > Account ID
Replace xxxxxx-xxxxxx-xxxxxx-xxxxxx with the API key, you can find this under Account Settings > General Settings > API Key
(Optional) Include the email address as a query parameter. As the customization operates in the background, it duplicates the entire guidebook and integrates additional assets. As a result, the API response doesn't contain details about any errors that may occur during this process. However, if you provide an email address, you'll receive notifications regarding any errors encountered.
For more information how to use GUIBO's reseller capabilities to automate the publishing of travel docs from operators to resellers, click here.
To create a download permission for a reseller per API, you need the Operator ID of the partner account. The operator ID is a three character unique identifier of each GUIBO account. Please pick the Operator ID from the partner list. You find it in the culumn OID.
Add the parameter resellerOid to you API request.
What happens then?
1) The release link for the traveller will be styled with the color from the reseller's partner account. This is configures in Account Settings > General Settings > Primary color
2) The logo of the booklet is replaced with the logo of the partner account (please note that this feature is still under development).
To automate the creation of one or multiple releases in GUIBO, CSV files can be sent to import@schneidergeo.com at any desired time intervals. These CSV files should include the following columns:
downloadcode
Unique ID of your guidebook
Language
“Downloadable from… Date”
“Valid until… Date”
Number of Devices
Follow these steps to get the automatic release creation running:
This step initiates the process by signaling GUIBO about your interest in utilizing the CSV import feature for automatic release creation via your csv files. Find your Servicedesk here: https://schneidergeo.atlassian.net/servicedesk/customer/portal/1
Send us the email address from which you will be sending the CSV files in the future. This is necessary to ensure that the CSV files come from a trusted source.
Provide a sample CSV file that includes all the above-mentioned columns. This is crucial for ensuring that your CSV format is compatible with our system.
GUIBO will configure the importer specifically for your account, ensuring that it can correctly process your CSV files.
Send your CSV file to import@schneidergeo.com for a test import. This step is crucial to verify that the importer is set up correctly for your account and that your CSV files are formatted correctly.
Check your test import in GUIBO to ensure that your booking has been correctly created. This verification step is important to catch any discrepancies early and address them before setting up regular imports.
Ensure that the CSV file format strictly follows the specified sorted columns requirements to avoid processing errors.
By following these steps, you can streamline the release creation process in GUIBO, making it more efficient and less prone to human error.
To personalize releases in GUIBO, it's essential that your content, such as hotels, is organized within a library. Each hotel (or any other asset) must be assigned a unique "external ID" by you. This ID is used to identify the hotel during the import process.
Title the ticket: “Personalized Release via CSV for COMPANYNAME.”
For adding specific POI's into releases, you will need to add one or more columns to your CSV file, corresponding to each POI you wish to include. Each of these additional columns should contain the external IDs of the POI's you're including in the release.
Import the new CSV file into GUIBO as usual. The process for importing remains the same, but the CSV now includes additional columns for personalized content.
After importing the CSV, test the created release in your release dashboard. Use the search function and enter the downloadcode of your imported release. Click on the blue "edit" button to get access to the customized guidebook.
