> 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/content-or-create-and-update-point-of-interests-pois.md).

# Content | Point-Of-Interests (POIs)

{% hint style="info" %}
Hotels are one kind of POIs in GUIBO. They can be created manually in GUIBO, also with the help of Google search and automatic import of data from Google.
{% endhint %}

### 1) Create POI

Prerequisite: You have created a library into which the hotels are to be imported. You have given the library a unique ID. In the following example it is the ID "<mark style="color:orange;">HOTELS</mark>".

![](/files/crWLdkqi7UEaDTuoq6UR)

* Replace <mark style="color:orange;">CCCCCC</mark> with the customer ID, you can find this under Account Settings > General Settings > Account ID
* Replace <mark style="color:orange;">xxxxxx-xxxxxx-xxxxxx-xxxxxx</mark> with the API key, you can find this under Account Settings > General Settings > API Key
* <mark style="color:orange;">HTL21344</mark> is an exemplaric custom ID of this hotel. With this ID it is easier to update the hotel via the interface.

```json
curl --location --request POST 'https://services.schneidergeo.com/content/geodata/poi' \
--header 'Content-Type: application/json' \
--header 'Authorization: xxxxxx-xxxxxx-xxxxxx-xxxxxx' \
--data-raw '
{
  "account":"CCCCCC",
   "library":{
      "customId":"MY_HOTELS_LIB"
   },
   "customId":"HTL21344",
  "names": {
    "de": "Alpenhotel Kronprinz",
    "en": "Alpenhotel Kronprinz"
  },
  "descriptions": {
    "de": "Unser Partnerhotel in Berchtesgaden",
    "en": "Our partner hotel in Berchtesgaden"
  },
  "lat": 47.62893,
  "lng": 12.99443,
  "icon": "hotel",
  "category": {
    "names": {
      "de": "Unterkunft",
      "en": "Accomodation"
    }
  },
  "attributes": {
    "phone": "+49 8652 6070",
    "web": "https://www.alpenhotel-kronprinz.de/"
  },
   "tags": [
        {
             "names": {
                   "de": "Unterkunft",
                   "en": "Accomodation"
               }
         }
    ]
}
'
```

#### Supported Icon Names for POIS:

attention\
fork\
hut\
info\
location\_large\
parking\
town\
water\
ballsports\
cablecar\_sports\
climbing\
crosscountryskiing\
cycling\
diving\_snorkeling\
fishing\
golfing\
hiking\
horseriding\
kitesurfing\
mountainbiking\
rowboat\
sailing\
skiing\
surfing\
swimming\
windsurfing\
festival\
movie\
museum\
music\
theater\
beach\
swimming\_indoor\
swimming\_outdoor\
apartment\
bed\_breakfast\
hotel\
doctor\
hospital\
pharmacy\
police\
cablecar\_poi\
castle\
church\
generic\
lake\
panoramicview\
peak\
ruins\
sight\
star\
tosee\
tourist\_info\
waterfall\
zoo\
text\
destination\
interimstep\
stagetown\
bar\
coffee\
deli\
distillery\_winery\
icecream\
pub\
restaurant\
conveniencestore\
mall\
supermarket\
airport\
bikerental\
busstop\
cablecar\_trans\
camping\
car\
carrental\
ferry\
parking\
parkinggarage\
taxi\
trainstation\
vespa

### B) Update POI

The update operation uses the same object as the create operation. Just some attributes are ignored and you can leave away:

* Change of category is ignored. Please use the apropriate endpoint
* Change of tags is ignored. Please use the apropriate endpoint
* Change of externalId is ignored.

This example updates the hotel from above with the  externen ID "HTL21344".

* Replace <mark style="color:orange;">CCCCCC</mark> with the customer ID, you can find this under Account Settings > General Settings > Account ID.
* Replace <mark style="color:orange;">xxxxxx-xxxxxx-xxxxxx-xxxxxx</mark> with the API key, you can find this under Account Settings > General Settings > API Key

```json
curl --location --request PUT 'https://services.schneidergeo.com/content/geodata/poi/CCCCCC/HOTELS/HTL21344' \
--header 'Authorization: xxxxxx-xxxxxx-xxxxxx-xxxxxx' \
--header 'Content-Type: application/json' \
--data-raw '
{
  "names": {
    "de": "Hotel Post",
    "en": "Hotel Post"
  },
  "descriptions": {
    "de": "Unser Partnerhotel in Salzburg",
    "en": "Our partner hotel in Salzburg"
  },
  "lat": 47.9455079,
  "lng": 12.9364846,
  "icon": "hotel",
  "attributes": {
    "phone": "+43 6272 4422",
    "web": "https://hotelpost.at"
  }
}
'
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.guibo.travel/developers/content-api/content-or-create-and-update-point-of-interests-pois.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.