> 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/access-your-customer-data.md).

# Access Your Customer Data

Once Your Customer has successfully completed the Onboarding Flow and granted Consent so that you, as The Client, can access their data, their Consent status will have changed.

You can then use the Consent ID when calling API.1 to retrieve data from Your Customer's Accounting System.

**What you need for each request:** the Consent ID and the API Key you created in the Client Portal. Use them to access any API.1 endpoint and filter or list invoices. Accounting API requests are scoped by Consent: the Consent ID is included in the request path (for example `.../consents/{consentId}/...`). See the [API Reference](https://apidocs.zwapgrid.com/) for the exact URL structure.

For full endpoint details, see the [API Reference](https://apidocs.zwapgrid.com/) section of our documentation.


---

# 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/access-your-customer-data.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.