> For the complete documentation index, see [llms.txt](https://docs.bless.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bless.net/blessnet-api/addresses-address-vaults.md).

# /addresses/:address/vaults

{% hint style="info" %}
You need an API key for this call.\
\
Please reach out to the Blessnet team to get setup.
{% endhint %}

<mark style="color:green;">`GET`</mark>`/addresses/:address/vaults`

The `/addresses/:address/vaults` endpoint retrieves a list of vaults associated with a specific delegate.

### **Headers**

| Name        | Value        |
| ----------- | ------------ |
| `x-api-key` | Your API key |

### **Path Variables**

<table><thead><tr><th width="215">Name</th><th width="130">Mandatory?</th><th width="119">Default</th><th>Value</th></tr></thead><tbody><tr><td><code>:address</code></td><td>Yes</td><td></td><td>The delegate address you are querying</td></tr></tbody></table>

### **Params**

<table><thead><tr><th width="215">Name</th><th width="130">Mandatory?</th><th width="119">Default</th><th>Value</th></tr></thead><tbody><tr><td><code>chain</code></td><td>No</td><td><code>mainnet</code></td><td>The chain type we are working with, either <code>mainnet</code> or <code>sepolia</code></td></tr><tr><td><code>permission</code></td><td>No</td><td><code>1</code> (all)</td><td>The permission Id we need to match, e.g. <code>4</code> Voting.</td></tr><tr><td><code>sourceChain</code></td><td>No</td><td><code>0</code> (any)</td><td>If we want to restrict results to a given source chain, e.g. for mirrored delegations from Ethereum mainnet we use <code>1</code>.</td></tr><tr><td><code>source</code></td><td>No</td><td><code>""</code> (any)</td><td>If we want to limit to a given source protocol, e.g. for EPS v2 we use <code>EPSV2</code>.</td></tr></tbody></table>

### **Response Body**

| Name     | Type    | Description                    |
| -------- | ------- | ------------------------------ |
| `vaults` | `array` | The valid vaults for that user |

### **Example Request**

```
GET https://api.bless.net/addresses/0x1633C7bD958E2789b51721d5C19441C237919dDa/vaults
```

### **Response**

{% tabs %}
{% tab title="200" %}

```json
{
  "vaults": [
    "0x1633C7bD958E2789b51721d5C19441C237919dDa",
    "0x4DF151f6Fa781E7C5f0B10d0c653E7b813cBb65E",
    "0x3d2996Ae16006101Abd515B11b6A836Ce254507c",
    "0x7008f1dA67c7bA098e9a67C328948f6e1710FFDc"
  ]
}
```

{% endtab %}

{% tab title="400" %}

```json
{
  "message": "Please provide chainId and delegate address as query parameters."
}
```

{% endtab %}
{% endtabs %}


---

# 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.bless.net/blessnet-api/addresses-address-vaults.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.