> 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/api-keys/usage.md).

# Usage

To access API.1 (Consent API and Accounting API), you must create an API Key. You create and manage API Keys in the [Client Portal](/client-portal/api-keys.md) per [environment](/client-portal/environments.md).

### Pass the key in requests

When you call API.1, pass your API Key in every request using the `x-api-key` HTTP header:

```
x-api-key: YOUR_API_KEY_HERE
```

Replace `YOUR_API_KEY_HERE` with the key you created in the Client Portal. Use a **Development** key for Development consents and sandbox data (e.g. Test.1); use a **Production** key for Production consents and live data from Your Customer's Accounting Systems.

For full request conventions, correlation IDs, and authentication, see [Get Started](/get-started/get-started.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.zwapgrid.com/client-portal/api-keys/usage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.