# API Keys

API Keys are required to call API.1 (Consent API and Accounting API). You create and manage API Keys in the Client Portal per [environment](/client-portal/environments.md). For how to use your key in API.1 requests, see [Usage](/client-portal/api-keys/usage.md).

### Create Development API Key

Create a **Development** API Key for non-production use—e.g. when building or testing your integration. Development keys let you create Development Consents and access sandbox data. For how to use the key in requests, see [Usage](/client-portal/api-keys/usage.md). For the full lifecycle, see [API Key Lifecycle](/client-portal/api-keys/api-key-lifecycle.md).

### Create Production API Key

Create a **Production** API Key when you are ready to go live. Production keys let you create Production Consents and access real data from Your Customer's Accounting Systems. Store it securely—see [Security](/client-portal/api-keys/security.md). For creation and lifecycle, see [API Key Lifecycle](/client-portal/api-keys/api-key-lifecycle.md).

### Naming and expiry

When creating an API Key you can set a **descriptive name** and an **expiry**. For details and recommendations on expiry and rotation, see [API Key Lifecycle](/client-portal/api-keys/api-key-lifecycle.md).

### Delete API Key

You can delete an API Key from the Client Portal. Once deleted, it can no longer be used for API.1 requests. For the full lifecycle and rotation steps, see [API Key Lifecycle](/client-portal/api-keys/api-key-lifecycle.md).

{% hint style="info" %}
**Expiry reminder emails**

To support business continuity, we send expiry reminder emails as an API Key's expiry date approaches and again 24 hours before it expires.
{% endhint %}


---

# Agent Instructions: 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.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.