# Get Fee Recommendations Solana

Through this endpoint customers can obtain recommended Solana transaction fees. Recommendations are computed in real time by taking the 25th, 50th and 75th percentiles of recent non-zero priority fees (in micro-lamports per compute unit) observed across a recent slot window, alongside the constant base fee per signature and the default and maximum compute unit limits. Solana has no mempool, so recommendations are derived from recently observed prioritization fees rather than pending-transaction data.

- **Endpoint:** `GET https://rest.cryptoapis.io/blockchain-fees/solana/{network}/mempool`
- **Authentication:** `x-api-key` header
- **Credits cost:** 90 credits for 1 result by default; per blockchain: Solana: 90
- **Documentation page:** https://developers.cryptoapis.io/v-2.2024-12-12-175/RESTapis/blockchain-fees-solana/get-fee-recommendations-solana/get

## Path parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `network` | string | yes | Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while a network like "devnet" is a test network. Allowed values: `devnet`, `mainnet`. |

## Query parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `context` | string | no | In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user. |

## Responses

| Status | Description |
| --- | --- |
| 200 | The request has been successful. |
| 400 | 400 |
| 401 | 401 |
| 402 | 402 |
| 403 | 403 |
| 404 | The provided resource is not found |
| 409 | The data provided seems to be invalid. |
| 415 | The selected Media Type is unavailable. The Content-Type header should be 'application/json'. |
| 422 | Your request body for POST requests must have a structure of { data: { item: [...properties] } } |
| 429 | The request limit has been reached. There can be maximum {requests} requests per {seconds} second(s) made. Please contact our team via email if you need more or upgrade your plan. |
| 500 | An unexpected server error has occurred, we are working to fix this. Please try again later and in case it occurs again please report it to our team via email. |

### Example 200 response

```json
{
  "apiVersion": "2024-12-12",
  "requestId": "601c1710034ed6d407996b30",
  "context": "yourExampleString",
  "data": {
    "item": {
      "baseFeePerSignature": {
        "unit": "lamports",
        "value": "5000"
      },
      "computeUnitPerInstruction": {
        "default": 200000,
        "max": 1400000
      },
      "priorityFeePerComputeUnit": {
        "fast": "100000",
        "slow": "1",
        "standard": "10000",
        "unit": "microLamports"
      }
    }
  }
}
```

### 200 response fields

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `apiVersion` | string | yes | Specifies the version of the API that incorporates this endpoint. |
| `requestId` | string | yes | Defines the ID of the request. The `requestId` is generated by Crypto APIs and it's unique for every request. |
| `context` | string | no | In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. `context` is specified by the user. |
| `data` | object | yes |  |
| `data.item` | object | yes |  |
| `data.item.baseFeePerSignature` | object | yes |  |
| `data.item.baseFeePerSignature.unit` | string | yes | Unit of the base fee, e.g. lamports |
| `data.item.baseFeePerSignature.value` | string | yes | Base fee per signature in lamports (currently 5000) |
| `data.item.computeUnitPerInstruction` | object | yes |  |
| `data.item.computeUnitPerInstruction.default` | integer | yes | Default compute unit limit per instruction (200000) |
| `data.item.computeUnitPerInstruction.max` | integer | yes | Maximum compute unit limit per transaction (1400000) |
| `data.item.priorityFeePerComputeUnit` | object | yes |  |
| `data.item.priorityFeePerComputeUnit.fast` | string | yes | Recommended fast priority fee per compute unit in micro-lamports (75th percentile across the recent slot window) |
| `data.item.priorityFeePerComputeUnit.slow` | string | yes | Recommended slow priority fee per compute unit in micro-lamports (25th percentile across the recent slot window) |
| `data.item.priorityFeePerComputeUnit.standard` | string | yes | Recommended standard priority fee per compute unit in micro-lamports (50th percentile across the recent slot window) |
| `data.item.priorityFeePerComputeUnit.unit` | string | yes | Unit of priority fees, e.g. microLamports |
