> 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 | 3. Points Of Interest (POIs)

Hotels and other POIs can be imported into GUIBO automatically via API. A common use case is syncing hotels from a booking system to automatically attach booked accommodations to a guest's guidebook.

{% 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 %}

Create, Read, Update, and Delete Points of Interest (POIs) in a geodata library.  Methods may require your **account ID**  and **API key**.  In the curl examples on this page:

* Replace <mark style="color:orange;">CCCCCC</mark> or `{account}` with your **account ID**. See [Overview](https://docs.guibo.travel/developers/overview#prerequisites) to find your **account ID**.
* Replace <mark style="color:orange;">xxxxxx-xxxxxx-xxxxxx-xxxxxx</mark> with the **API key**.  See [Overview](https://docs.guibo.travel/developers/overview#prerequisites) to find your **API key**.
* Replace placeholders such as `{link}` or `{customId}` as described in their respective sections.

### A) Create POI

Create a **POI** with a **Custom ID**. The `customId` is the stable id for this POI when you update, delete or reference it from other GUIBO APIs (for example an **On-Demand Release** or a **Guidebook**).

Prerequisite: an existing geodata library with a **Custom ID** (`library.customId`, see [Create Geodata Library](https://docs.guibo.travel/developers/content-api/content-or-create-library-or-guidebook)). &#x20;

* Set `library.customId` in the request to that library's **Custom ID**. In the following example the **Custom ID** is "<mark style="color:orange;">HOTELS</mark>".

![](https://4249329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE2a888ltdx6dUekSgs4U%2Fuploads%2FLdDBMpwSWM3LD8TCBrbO%2Fgrafik.png?alt=media\&token=6c72bd92-8296-4b7c-a711-c9497e77793c)

* Required in body: **account ID**, `library.customId`, the POI's `customId`, `names`, `descriptions`, `lat`, `lng`, and `icon`.

{% hint style="info" %}
Content POI coordinates use `lat` / `lng`.  **On-Demand Release** inline payloads use `lon` for longitude.  Map `lng` → `lon` when reusing Content data in a release.
{% endhint %}

* Optional fields:  `attributes` (to update, see [C) Update POI](#c-update-poi)), `tags` (update via [Content | 4. Geodata Properties](https://docs.guibo.travel/developers/content-api/content-or-4.-geodata-properties)).

```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":"HOTELS"
   },
  "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": "Accommodation"
    }
  },
  "attributes": {
    "phone": "+49 8652 6070",
    "web": "https://www.alpenhotel-kronprinz.de/"
  },
   "tags": [
        {
             "names": {
                   "de": "Unterkunft",
                   "en": "Accommodation"
               }
         }
    ]
}
'
```

#### 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) Read POI

Read a POI using the POI's `link`.&#x20;

```shellscript
curl --location --request GET 'https://services.schneidergeo.com/content/geodata/poi/{link}' \
--header 'Authorization: xxxxxx-xxxxxx-xxxxxx-xxxxxx' \
--header 'Content-Type: application/json'
```

### C) Update POI

Update a POI using the same request body as Create.  Target the POI with your **account ID**, the POI's `customId`, and its library's `library.customId` in the body.  &#x20;

This `PUT` updates: `names`, `descriptions`, `lat`, `lng`, `icon`, and `attributes`.&#x20;

Also available via [Content | 4. Geodata properties](https://docs.guibo.travel/developers/content-api/content-or-4.-geodata-properties.md):

* `customId`: see [Content | 4. Geodata properties > A) Update Custom ID](https://docs.guibo.travel/developers/content-api/content-or-4.-geodata-properties#a-update-custom-id).
* `tags`: see [Content | 4. Geodata properties > B) Updating Tags](https://docs.guibo.travel/developers/content-api/content-or-4.-geodata-properties#b-updating-tags).

```bash
curl --location --request PUT 'https://services.schneidergeo.com/content/geodata/poi' \
--header 'Authorization: xxxxxx-xxxxxx-xxxxxx-xxxxxx' \
--header 'Content-Type: application/json' \
--data-raw '
{
  "account":"CCCCCC",
  "library":{
      "customId":"HOTELS"
   },
  "customId":"HTL21344",
  "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"
  }
}
'
```

### D) Delete POI

Delete a POI using your **account ID** and the asset's **custom ID**.  Delete moves the POI to trash.  Add the query parameter `force=true` to the URL to permanently delete it.

```bash
curl --location --request DELETE 'https://services.schneidergeo.com/content/geodata/account/{account}/external/{customId}' \
--header 'Authorization: xxxxxx-xxxxxx-xxxxxx-xxxxxx' \
--header 'Content-Type: application/json' 
```


---

# 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/content-or-create-and-update-point-of-interests-pois.md?ask=<question>&goal=<user_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.
