> For the complete documentation index, see [llms.txt](https://docs.clique.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clique.tech/clique-wallet/features-and-capabilities/api-keys-and-programmatic-access.md).

# API Keys and Programmatic Access

Clique Wallet provides comprehensive programmatic access through API keys, enabling automated operations and integration with external systems.

#### API Key Permissions

API keys support granular permission scopes:

* **View (1)**: Read-only access to account information, wallet addresses, and transaction history
* **View + Trading (3)**: View permissions plus the ability to execute trading operations
* **View + Transfer (5)**: View permissions plus the ability to transfer assets
* **View + Trading + Transfer (7)**: Full access to all operations

Permissions are enforced at the API level, ensuring that operations requiring specific permissions are blocked if the API key doesn't have the necessary access.

#### IP Whitelisting

API keys can be configured with IP address whitelists, restricting usage to specific IP addresses. This provides an additional layer of security for sensitive operations. IP whitelisting is optional and can be configured when creating or updating an API key.

#### API Key Management

Users can manage their API keys through authenticated endpoints:

* **Create**: Generate new API keys with specific permissions and IP whitelists
* **List**: View all API keys associated with the account
* **Activate/Deactivate**: Temporarily disable API keys without deleting them
* **Delete**: Permanently remove API keys

**Important**: API keys are only displayed once during creation. If you lose an API key, you must create a new one.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.clique.tech/clique-wallet/features-and-capabilities/api-keys-and-programmatic-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.