> 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/get-started/onboard-your-customer.md).
# Onboard Your Customer
To integrate Your Customer with API.1, you must first use the Consent API to create a Consent - you then use the generated Consent ID in order to invite Your Customer to share data from their Accounting System using the Onboarding Flow.
Once Your Customer has accepted the Consent you can use API.1 to consume data from their Accounting System from within Your Platform.
End-to-end flow: consent, onboarding, and data access.
## Onboard from your backend
If your client backend owns the connection experience, use [Headless Onboarding (Preview)](/onboarding-flow/headless-onboarding.md). It describes the shared workflow and the request bodies for supported systems. Provider login and customer approval still apply where required.
---
# 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/get-started/onboard-your-customer.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.
