> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/june5-3.7/en/web-api/swagger-web-api-dokumentation.md).

# Swagger Web API Documentation

The SWAGGER Web API documentation is accessible under:

| Protocol | Url                                          |
| -------- | -------------------------------------------- |
| HTTP     | http\://{Domain and port of server}/Swagger  |
| HTTPS    | https\://{Domain and port of server}/Swagger |

If the JUNE5 demo server is used, the following address should be applied:

<http://portal.videc.info/swagger>

The image below shows the user interface of the SWAGGER Web API documentation.

![](/files/asPVH8P6VQK7OOmbIlEB)

In the text field "api\_key", enter the token that was assigned by the server.

![](/files/7XYEDpjlbyjw2i24XZfL)

With "Try it out!" the request can be sent to the server. In "Logon" and "Password" the username and password must be transmitted.

The token can then be taken from the server's response and must be copied into the text field above.

After that, all further HTTP requests can be tested.


---

# 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:

```
GET https://docs.videc.de/june5-3.7/en/web-api/swagger-web-api-dokumentation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.