> For the complete documentation index, see [llms.txt](https://docs.guibo.travel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guibo.travel/developers/content-api/how-to-synchronize-data-with-your-it-systems.md). # HOW TO synchronize data with your IT systems In case you already have a system that helps you manage Point-Of-Interests, Routes, Travel Information, etc. you can still use the power of GUIBO to improve your operations. If you already use an external system (such as a CMS, PIM, or internal database) to store and manage your Points of Interest (POIs), Routes, or Travel Information, you can seamlessly integrate it with GUIBO to streamline your operations. ### How Synchronization Works In GUIBO, external data should be imported and synced directly into your Libraries. Libraries serve as your central repository in GUIBO, making synced content instantly available for reuse. Once your assets reside in a Library, you can seamlessly pull them into custom Guidebooks and Itineraries for your customers. ### Recommended Library Structure To keep your synchronized data organized and easy to access when building guidebooks, we recommend setting up dedicated libraries for each asset type. 🔑 Best Practice: Assign Custom IDs Assign a Custom ID to every library you create. Using unique Custom IDs allows your automated scripts and sync processes to reliably target and update specific libraries via the GUIBO API without hardcoding database IDs. GUIBO uses two main types of libraries: * Geodata Libraries: For location-based assets that contain geographic coordinates, routes, or addresses. * Text Libraries: For structured text, general articles, and non-geographic content. #### Essential Libraries to Set Up * Accommodation Library *(Geodata Library)* Stores hotels, guesthouses, campsites, and other lodging options along with their location and amenity details. * POI Library *(Geodata Library)* Contains Points of Interest such as landmarks, restaurants, viewpoints, and activity spots. * Routes Library *(Geodata Library)* Houses GPS tracks, walking trails, cycling routes, and transfer paths. * Destination Library *(Geodata Library)* Holds broader geographic regions, towns, the destiation of the trips you are offering. * General Information Library *(Text Library)* Stores reusable text snippets, packing lists, travel tips, local rules, and emergency contacts. 💡 Pro Tip: Sub-dividing Libraries As your catalog grows, you can create multiple instances of a library type to keep assets organized by region, language, activity type, or supplier (e.g., *POI Library – Italy* vs. *POI Library – Norway*). [Create Library per API](/developers/content-api/content-or-create-library-or-guidebook.md#a-create-geodata-library) [Create Library manually](/get-started/getting-started/prepare-library.md#step-1-create-route-library) After you successfully created your libraries, you can manage your assets **CREATE** [Poi](/developers/content-api/content-or-create-and-update-point-of-interests-pois.md#id-1-create-poi) / [Route](/developers/content-api/content-or-create-and-update-routes.md#a-create-route) / [Text](/developers/content-api/content-or-create-text-page.md#a-create-textpage-in-library)page **READ** [Poi](/developers/content-api/content-or-create-and-update-point-of-interests-pois.md#b-read-poi) / [Route](/developers/content-api/content-or-create-and-update-routes.md#b-read-route) /[Textpage](/developers/content-api/content-or-create-text-page.md#b-read-textpage) **UPDATE** [Poi](/developers/content-api/content-or-create-and-update-point-of-interests-pois.md#b-update-poi) / [Route](/developers/content-api/content-or-create-and-update-routes.md#c-update-route) / [Textpage](/developers/content-api/content-or-create-text-page.md#c-update-textpage) **DELETE** [Poi](/developers/content-api/content-or-create-and-update-point-of-interests-pois.md#c-delete-poi) / [Route](/developers/content-api/content-or-create-and-update-point-of-interests-pois.md#c-delete-poi) / [Textpage](/developers/content-api/content-or-create-text-page.md#d-delete-textpage) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.guibo.travel/developers/content-api/how-to-synchronize-data-with-your-it-systems.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.