> 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/security.md).

# Security

API Key security is your responsibility. Follow these practices to keep keys safe.

### Store and protect your key

Zwapgrid does not store your API Key after creation. **Copy the key when it is shown** and store it securely. Limit who has access to see or use the key.

### Where not to use API Keys

Do **not** use API Keys in front-end code or anywhere the key could be exposed, including:

* Web browsers or client-side applications
* Public repositories or shared code
* Logs, URLs, or error messages

Use API Keys only in secure server-side or backend environments where the key cannot be exposed to end users or the public.

### Refresh keys regularly

We encourage you to refresh your API Keys regularly as a security best practice. Create a new key, update your applications to use it, then delete the old key. See [API Key Lifecycle](/client-portal/api-keys/api-key-lifecycle.md) for creating and deleting keys.

{% hint style="danger" %}
It is your responsibility to keep your API Keys safe.
{% endhint %}


---

# 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/security.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.