> 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/consents/create-consent.md).
# Create Consent
{% hint style="info" %}
**How do you create Consent?**
The Client can create Consent using API.1 before you invite Your Customer to the Onboarding Flow to share data from their Accounting System.
{% endhint %}
### Create a consent using API.1
The Client must use API.1 to create a Consent which will generate a Consent ID.
#### Providing System Settings during Consent Creation
When creating a Consent, you can optionally specify which published system settings to use for each [configurable Accounting System](/client-portal/systems.md#configure-system-settings). This allows you to direct Your Customer to use specific credentials and configuration.
Include the `systemsSettings` object in your API request, mapping each system to its corresponding system settings ID:
```json
{
"name": "{{consentName}}",
"systemsSettings": {
"fortnox": "{{systemSettingsId}}"
}
}
```
### Onboarding Flow
The Client must direct Your Customer to the Onboarding Flow requesting Consent to access data from their Accounting System.
Your Customer will use the Onboarding Flow to connect to their Accounting System.
Create Consent flow.
---
# 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/consents/create-consent.md?ask=&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.
