> ## Documentation Index > Fetch the complete documentation index at: https://docs.kraken.com/llms.txt > Use this file to discover all available pages before exploring further. # Allocate Earn Funds > Allocate funds to the Strategy. Requires the `Earn Funds` API key permission. The amount must always be defined. This method is asynchronous. A couple of preflight checks are performed synchronously on behalf of the method before it is dispatched further. The client is required to poll the result using the `/0/private/Earn/AllocateStatus` endpoint. There can be only one (de)allocation request in progress for given user and strategy at any time. While the operation is in progress: 1. `pending` attribute in `/Earn/Allocations` response for the strategy indicates that funds are being allocated, 2. `pending` attribute in `/Earn/AllocateStatus` response will be true. Following specific errors within `Earnings` class can be returned by this method: - Minimum allocation: `EEarnings:Below min:(De)allocation operation amount less than minimum` - Allocation in progress: `EEarnings:Busy:Another (de)allocation for the same strategy is in progress` - Service temporarily unavailable: `EEarnings:Busy`. Try again in a few minutes. - User tier verification: `EEarnings:Permission denied:The user's tier is not high enough` - Strategy not found: `EGeneral:Invalid arguments:Invalid strategy ID` ## OpenAPI ````yaml /openapi/spot-rest.yaml post /private/Earn/Allocate openapi: 3.0.0 info: title: REST API version: 1.1.0 description: '' servers: - url: https://api.kraken.com/0 description: Production Server security: - API-Key: [] API-Sign: [] tags: - name: Market Data - name: Account Data - name: Trading - name: Funding - name: Subaccounts description: >- Subaccounts are currently only available to institutional clients. Please contact your Account Manager for more details. - name: Earn description: > The earn API allows interacting with all of Kraken's yield generating products. It replaces the old `/staking` part of the API. The different available earn products are represented by earn strategies. This corresponds to the legacy `Staking/Assets`. `Stake`/`Unstake` are replaced by `Allocate`/`Deallocate`. ### Overview of the available endpoints under `/Earn`: - `Strategies` - list all earn strategies for which you are eligible or have a balance. - `Allocations` - lists the balance in your earn account for each strategy. Requires the `Query Funds` API key permission. - `Allocate`/`Deallocate` - allocate/deallocate to an earn strategy through an async operation. Requires the `Earn Funds` API key permission. - `AllocateStatus`/`DeallocateStatus` - verifies the state of the last allocation/deallocation. Requires the `Earn Funds` or `Query Funds` API key permission. ### Example usage: ### Determine which funds are earning rewards: 1. Call `Strategies` to obtain information about the relevant strategy. The `lock_type` field shows whether bonding/unbonding funds are earning yield. The relevant fields are `bonding_rewards`/`unbonding_rewards`. 2. Call `Allocations` for the relevant strategy. From the previous step, for strategies where bonding/unbonding does not earn yield, substract these balances from `amount_allocated.total` to determine which balances are currently earning. ### Get allocatable balance: Call `/0/private/BalanceEx`, subtract `hold_trading` amount. Remaining balance is available for allocation to a strategy. ### Geo restrictions: Some earn strategies are not available in all geographic regions. `Strategies` will return only strategies available to the caller. - name: Transparency paths: /private/Earn/Allocate: post: tags: - Earn summary: Allocate Earn Funds description: >- Allocate funds to the Strategy. Requires the `Earn Funds` API key permission. The amount must always be defined. This method is asynchronous. A couple of preflight checks are performed synchronously on behalf of the method before it is dispatched further. The client is required to poll the result using the `/0/private/Earn/AllocateStatus` endpoint. There can be only one (de)allocation request in progress for given user and strategy at any time. While the operation is in progress: 1. `pending` attribute in `/Earn/Allocations` response for the strategy indicates that funds are being allocated, 2. `pending` attribute in `/Earn/AllocateStatus` response will be true. Following specific errors within `Earnings` class can be returned by this method: - Minimum allocation: `EEarnings:Below min:(De)allocation operation amount less than minimum` - Allocation in progress: `EEarnings:Busy:Another (de)allocation for the same strategy is in progress` - Service temporarily unavailable: `EEarnings:Busy`. Try again in a few minutes. - User tier verification: `EEarnings:Permission denied:The user's tier is not high enough` - Strategy not found: `EGeneral:Invalid arguments:Invalid strategy ID` operationId: allocateStrategy requestBody: content: application/json: schema: description: Allocation amount in asset specified in the strategy type: object properties: nonce: $ref: '#/components/schemas/nonce' amount: description: The amount to allocate. type: string strategy_id: description: >- A unique identifier of the chosen earn strategy, as returned from `/0/private/Earn/Strategies`. type: string required: - amount - nonce - strategy_id example: amount: '4.3' nonce: 30295839 strategy_id: ESRFUO3-Q62XD-WIOIL7 required: true responses: '200': description: Response content: application/json: schema: type: object properties: error: $ref: '#/components/schemas/error' result: description: >- Will return `true` when the operation is successful, null when an error occurred. nullable: true type: boolean example: error: [] result: true components: schemas: nonce: description: Nonce used in construction of `API-Sign` header type: integer format: int64 error: type: array items: description: Kraken API error type: string example: EGeneral:Invalid arguments securitySchemes: API-Key: type: apiKey description: The "API-Key" header should contain your API key. name: API-Key in: header API-Sign: type: apiKey description: >- Authenticated requests should be signed with the "API-Sign" header, using a signature generated with your private key, nonce, encoded payload, and URI path. name: API-Sign in: header ````