> 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/releases-api/release-or-add-document-to-release.md).

# Release | Add document to release

When you add PDF documents to a release, they will be offine available in the App and they will be accessible under the private release link for your customer.

Adressed by operator account and operator's downloadcode:

<mark style="color:green;">`POST`</mark> `https://services.schneidergeo.com/content/release/{account}/{downloadCode}/document/v2?description=Hotelvoucher`&#x20;

Addressed by Release ID:

<mark style="color:green;">`POST`</mark> `https://services.schneidergeo.com/content/release/{id}/document?description=Hotelvoucher`&#x20;

Adding one PDF document to guidebook release. For multiple documents, please call this endpoint multiple times

#### Path Parameters

<table><thead><tr><th>Name</th><th width="174">Type</th><th>Description</th></tr></thead><tbody><tr><td>account<mark style="color:red;">*</mark></td><td>String</td><td>Your account ID, you can find this under Account Settings > General Settings > Account ID</td></tr><tr><td>downloadCode<mark style="color:red;">*</mark></td><td>String</td><td>The downloadCode for the release</td></tr></tbody></table>

#### Query Parameters

| Name                                          | Type   | Description                              |
| --------------------------------------------- | ------ | ---------------------------------------- |
| description<mark style="color:red;">\*</mark> | String | The title or description of the document |

#### Headers

| Name                                            | Type   | Description                                                                         |
| ----------------------------------------------- | ------ | ----------------------------------------------------------------------------------- |
| Authorization<mark style="color:red;">\*</mark> | String | Your API key, you can find this under Account Settings > General Settings > API Key |

#### Request Body

| Name                                   | Type   | Description                     |
| -------------------------------------- | ------ | ------------------------------- |
| file<mark style="color:red;">\*</mark> | String | The PDF document to be uploaded |

Example:

```
curl --location --request POST 'https://services.schneidergeo.com/content/release/{account}/{downloadCode}/document?description=Train Ticket' \
--header 'Authorization: aiose9-98erjsd-0a9s8duj-ds8sss' \
--form 'file=@"/home/fritz/Documents/7HTUUL.pdf"'
```


---

# 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/releases-api/release-or-add-document-to-release.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.