> ## Documentation Index > Fetch the complete documentation index at: https://docs.portalhq.io/llms.txt > Use this file to discover all available pages before exploring further. # Get the testnet funding configuration > Returns the funding configuration for every supported testnet chain and token pair. Each entry describes the per-request maximum and the cumulative maximum allowed over a rolling window, along with the window length in minutes. These are the same limits the `POST /clients/me/fund` endpoint enforces, so you can use this endpoint to discover the supported pairs and their limits before requesting funds. The response is a JSON array of configuration entries. Amounts are returned as decimal strings expressed in whole token units (not base units). ## OpenAPI ````yaml /openapi/client-api.yaml get /clients/me/fund/config openapi: 3.1.0 info: title: Portal Client API version: '3.0' description: > The Portal Client API provides endpoints for managing wallets, building transactions, and interacting with blockchain networks. All endpoints require authentication via a Client API Key or Client Session Token (CST) passed as a Bearer token. ## Base URL `https://api.portalhq.io/api/v3` ## Authentication Include your Client API Key or Client Session Token as a Bearer token in the `Authorization` header of every request. ## Chain ID Format Chain parameters use either friendly names (e.g. `ethereum`, `solana`) or CAIP-2 format (e.g. `eip155:1`, `solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`). When using CAIP-2 format in URLs, ensure the colon is URI-encoded (`%3A`). servers: - url: https://api.portalhq.io/api/v3 description: Production security: - bearerAuth: [] tags: - name: Clients description: Core client management endpoints - name: Wallet description: >- Read wallet state — balances, NFTs, transaction history, capabilities, and transaction details - name: Transactions description: Build, broadcast, and evaluate blockchain transactions - name: Funding description: Fund wallets with testnet tokens - name: Wallet Shares description: Manage signing and backup share pairs - name: Delegations description: Manage token approvals, revocations, and delegated transfers - name: Session Keys description: Manage EIP-7702 session keys for smart accounts - name: 0x description: Token swap endpoints powered by the 0x protocol - name: Yield.xyz description: Yield opportunities and staking actions powered by Yield.xyz - name: Li.Fi description: Cross-chain swaps and bridging powered by Li.Fi - name: Blockaid description: Transaction and address security scanning powered by Blockaid - name: Hypernative description: >- Transaction, address, token, and NFT security scanning powered by Hypernative - name: Noah description: KYC onboarding, payins, and payouts powered by Noah - name: Meld description: Buy and sell crypto with fiat through aggregated providers powered by Meld - name: Due description: Payins, payouts, virtual accounts, and FX powered by Due - name: EIP-7702 description: EIP-7702 account type detection and authorization management - name: Deprecated description: >- Legacy endpoints scheduled for removal. Use the newer equivalents listed in each endpoint's description. paths: /clients/me/fund/config: get: tags: - Funding summary: Get the testnet funding configuration description: > Returns the funding configuration for every supported testnet chain and token pair. Each entry describes the per-request maximum and the cumulative maximum allowed over a rolling window, along with the window length in minutes. These are the same limits the `POST /clients/me/fund` endpoint enforces, so you can use this endpoint to discover the supported pairs and their limits before requesting funds. The response is a JSON array of configuration entries. Amounts are returned as decimal strings expressed in whole token units (not base units). operationId: getFundConfig responses: '200': description: The testnet funding configuration. content: application/json: schema: type: array items: $ref: '#/components/schemas/FundConfigEntry' example: - chainId: eip155:11155111 token: USDC displayName: Ethereum Sepolia maxPerRequest: '0.1' maxPerWindow: '0.1' windowMinutes: 1440 - chainId: eip155:10143 token: MON displayName: Monad Testnet maxPerRequest: '1' maxPerWindow: '1' windowMinutes: 1440 - chainId: solana:EtWTRABZaYq6iMfeYKouRu166VU2xqa1 token: USDC displayName: Solana Devnet maxPerRequest: '0.1' maxPerWindow: '0.1' windowMinutes: 1440 '401': description: Unauthorized - invalid or missing authentication token content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: FundConfigEntry: type: object description: A single supported testnet funding configuration entry. properties: chainId: type: string description: The chain ID in CAIP-2 format (e.g. `eip155:11155111` for Sepolia). token: type: string description: The token symbol for this entry (e.g. `USDC`, `ETH`, `NATIVE`). displayName: type: string description: Human-readable name for the chain (e.g. `Ethereum Sepolia`). maxPerRequest: type: string description: > Maximum amount that a single fund request may specify for this chain and token, as a decimal string in whole token units. maxPerWindow: type: string description: > Maximum cumulative successful funding allowed for this chain and token within the rolling window, as a decimal string in whole token units. windowMinutes: type: integer description: >- Length of the rolling window in minutes over which `maxPerWindow` is applied. ErrorResponse: type: object properties: error: type: string description: Error message describing what went wrong securitySchemes: bearerAuth: type: http scheme: bearer description: > Client API Key or Client Session Token (CST). Pass as a Bearer token in the Authorization header. ````