Content | 1. Library
Libraries are the central hubs where you manage your POIs, Routes, and Textpages. Any asset stored in a library can be reused across multiple guidebooks—allowing you to update content in one place and
A) Create Geodata Library
Geodata libraries store both Routes and POIs, though we recommend maintaining separate libraries for each. Assigning a customId to a library makes it easy to reference during a Release—simply pass this value into the externalGuidebookId parameter, as detailed below.
Replace CCCCC with the Account ID, you can find this under Account Settings > General Settings > Account ID
You can find the API key under Account Settings > General Settings > API Key
curl --location -X POST 'https://services.schneidergeo.com/content/library/geodata' \
--header 'Authorization: xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx' \
--header 'Content-Type: application/json' \
--data '{
"account":"CCCCCC",
"customId":"ABCABC",
"names":{
"de":"Transalp mit dem Gravelbike",
"en":"TRANS-ALP ON GRAVEL BIKE"
}
}'Headers
Authorization*
String
API key
B) Create Text Library
Text libraries store Textpages and Weblinks. Assigning a customId to a library makes it easy to reference during a Release—simply pass this value into the externalGuidebookId parameter, as detailed below.
Replace CCCCC with the Account ID, you can find this under Account Settings > General Settings > Account ID
You can find the API key under Account Settings > General Settings > API Key
B) Delete Library
Replace GGGGGG with the Guidebook ID,
You can find the API key under Account Settings > General Settings > API Key
Headers
Authorization*
String
API key
Last updated