> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/inoxision-archiv-connector/inoxisionarchivconnector_en_us/search-the-archive/start-a-search.md).

# Start a search

Run an archive search from the Inoxision Search page.

Search for **Inoxision Search**. The same page is also found as **Archive Search** and **Inoxision**. In a German interface the page caption is **Inoxision Suche**.

{% stepper %}
{% step %}

### Search text

Enter the term in **Search Text**. That can be a document number, a customer or vendor number, or another search text.
{% endstep %}

{% step %}

### Narrow the search

The other fields are optional:

* **Document Type Filter** limits the document type.
* **Document No. Filter** limits the document number.
* **Address No. Filter** limits the address number.
* **From Date** and **To Date** limit the period.
  {% endstep %}

{% step %}

### Run the search

Choose **Search**. Results appear in the list below.
{% endstep %}
{% endstepper %}

The list includes document type, document number, document date, address, name, city, total, and archive date. Several of these columns keep their Inoxision names, such as **Belegart**, **Belegnummer**, and **Gesamtsumme**. The Inoxision id is the **IID** column.


---

# 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.solutioo.de/inoxision-archiv-connector/inoxisionarchivconnector_en_us/search-the-archive/start-a-search.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.