> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/client-portal/systems/setup-guides/kleer.md).

# Kleer

Set up a Zwapgrid-managed Kleer connection.

Kleer connections use the current Zwapgrid-managed setup. System Settings and custom scope selection are not available for Kleer.

## Before you start

You need the following from the Kleer company:

* An API token. The customer supplies this token.
* A positive Kleer company ID.

Contact [Kleer](https://api-doc.kleer.se/) to arrange API access before connecting the company.

## Connect Kleer

1. Create or open the relevant consent and choose Kleer in the onboarding flow.
2. Enter the API token and positive company ID.
3. Complete the connection and test the API.1 and Proxy.1 operations your product needs.

## Testing

Ask Kleer to arrange a dedicated test company and confirm its API host, token, and company ID. Confirm with Zwapgrid that the provided environment is supported before connecting it. Test access and credentials must be arranged with Kleer; do not assume a public, self-service sandbox.


---

# 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.zwapgrid.com/client-portal/systems/setup-guides/kleer.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.