# Address Airdrops Value

Returns the **total fiat value of unclaimed airdrops** for a given address on a supported network. To reveal the full details, you should redirect users to the corresponding address page on Drops.&#x20;

### Endpoints

#### Get Address Airdrops

<mark style="color:$primary;">GET</mark>  `/shared/v1/value/airdrops/:network/:address`

**Headers**

| Header      | Type   | Required | Description                     |
| ----------- | ------ | -------- | ------------------------------- |
| `x-api-key` | string | ✅        | Your API key for authentication |

**Path Parameters**

| Parameter | Type   | Required | Description                                                                  |
| --------- | ------ | -------- | ---------------------------------------------------------------------------- |
| `network` | string | ✅        | Network to query                                                             |
| `address` | string | ✅        | The wallet address to check (must be a valid address with the network param) |

**Example Requests**

**cURL - Ethereum Address**

```bash
curl -X GET "https://api.drops.bot/shared/v1/value/airdrops/evm/0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045" \
  -H "x-api-key: YOUR_API_KEY"
```

The following networks are supported for address airdrop queries:

| Network ID | Name                                                         |
| ---------- | ------------------------------------------------------------ |
| `evm`      | All EVM and L2 chains                                        |
| `solana`   | Solana                                                       |
| `move`     | Sui, Aptos, and all other Move Networks                      |
| `cosmos`   | Cosmos and all subnets (address must start with \`cosmos1\`) |
| `bitcoin`  | Bitcoin                                                      |
| `starknet` | Starknet                                                     |

### Response

#### 200 - Successful Response

```typescript
{
  "success": true,
  "data": AddressAirdropValueData
}
```

#### AddressAirdropValueData

| Field                    | Type    | Description                                                              |
| ------------------------ | ------- | ------------------------------------------------------------------------ |
| `airdropsCount`          | number  | Number of eligible airdrops for the given address                        |
| `totalValueUsd`          | number  | Total fiat value of unclaimed airdrops (in USD)                          |
| `totalValueUsdFormatted` | string  | Human-readable formatted string of the total value (e.g. "$123.45")      |
| `isUnknownUsdValue`      | boolean | True if the total value cannot be calculated (e.g. missing token prices) |
| `addressUrl`             | string  | URL to the Drops address page with details for the given address         |

#### Example Success Response

```json
{
  "success": true,
  "data": {
    "airdropsCount": 3,
    "totalValueUsd": 452.78,
    "totalValueUsdFormatted": "$452.78",
    "isUnknownUsdValue": false,
    "addressUrl": "https://www.drops.bot/address/0x1234abcd..."
  }
}
```

#### Example Response (unknown USD value of the airdrops)

Sometimes the value of the airdrops can’t be determined. For example, before TGE or if the total allocation is unknown.

```json
{
  "success": true,
  "data": {
    "airdropsCount": 2,
    "totalValueUsd": 0,
    "totalValueUsdFormatted": "$0",
    "isUnknownUsdValue": true,
    "addressUrl": "https://www.drops.bot/address/0x1234abcd..."
  }
}

```


---

# 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.drops.bot/api-reference/endpoints/address-airdrops-value.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.
