> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/gerate-per-restful-verbinden/restful-request-konfigurieren.md).

# Configure RESTful request

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/V8Ecift3bsrdvYtPDfAA/Docs_Verbindungen%20-%20Verbindungen%20Requst%20Details.png" alt=""><figcaption></figcaption></figure></div>

In this window, you can configure a GET request step by step. You can find out exactly what a request must look like in the documentation for the respective API.

<table><thead><tr><th width="106.33333333333331">Icon</th><th>Description</th><th>Details</th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Path</td><td>Path with the URL to the resource. The base URL is already filled in</td></tr><tr><td><strong>[B]</strong></td><td>Name</td><td>Name of the request</td></tr><tr><td><strong>[C]</strong></td><td>Interval</td><td>Specifies the period in seconds during which Eliona sends requests to the server</td></tr><tr><td><strong>[D]</strong></td><td>HTTP Method</td><td>The HTTP method of the request. Currently, only GET is available</td></tr><tr><td><strong>[E]</strong></td><td>Format</td><td>Select an existing format. This format determines how the incoming data is mapped. Learn more about ↗formats</td></tr><tr><td><strong>[F]</strong></td><td>Create new format</td><td>Displays the incoming data and provides the option to <a href="https://docs.buildings.ability.abb/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/ein-format-konfigurieren.md">↗ new format</a> to create.</td></tr><tr><td><strong>[G]</strong></td><td>Content</td><td>Configure request content</td></tr><tr><td><strong>[H]</strong></td><td>Add parameter</td><td>Creates a new parameter with key and value</td></tr><tr><td><strong>[I]</strong></td><td>key</td><td>Specify key</td></tr><tr><td><strong>[J]</strong></td><td>Value</td><td>Enter value</td></tr><tr><td><strong>[K]</strong></td><td>Save</td><td>Save request</td></tr></tbody></table>


---

# 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.buildings.ability.abb/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/gerate-per-restful-verbinden/restful-request-konfigurieren.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.
