> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/connectors/connectors/exact-online.md).

# Exact Online

Cloud business software for SMEs and their accountants

## Introduction

Exact Online is an online accounting and ERP software.

## Authentication

1. Before authentication Exact with Locoia, please ensure your user has all authentication, as per [here in Exact](https://start.exactonline.de/docs/MenuPortal.aspx?SsC=1).
2. You can simply use your Exact user credentials in Locoia to authenticate.

{% hint style="info" %}
**No** Exact app creation is needed by you. We did this for you.
{% endhint %}

## Good to know

The Exact API is very extensive, thus there are some extra tipps for working with the Exact Connector:

* The [documentation](https://start.exactonline.nl/docs/HlpRestAPIResources.aspx?SourceAction=10) is very important and it makes sense to use it, in parallel with the Connector Action
  * To find endpoints quickly, use the Endpoint Search field
  * There are almost always links to details for endpoints
  * `GET` and `POST` fields are not the same (fields are shown, by selecting a method at the top)
  * `!` means required field
* Many requests bodies are quite nested and often required fields and the nested structures need to be provided
* [Filtering works with OData Syntax](https://www.odata.org/documentation/odata-version-2-0/uri-conventions/) (don’t forget to set quotation marks); unfortunately there are no good examples in the documentation
* `POST` requests don't return response payload, instead a `GET` call needs to be made afterwards to get the actual data
* `POST` actions are not added in Locoia, as the format is quite custom, instead the POST Wildcard Action should be used
* In general there are lots of dependencies between entities


---

# 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.locoia.com/connectors/connectors/exact-online.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.
