> ## Documentation Index > Fetch the complete documentation index at: https://docs.grainfinance.co/llms.txt > Use this file to discover all available pages before exploring further. # Withdraw > Withdraws funds from a wallet to a configured beneficiary. Returns the ID of the created withdrawal fund transfer. ## OpenAPI ````yaml POST /wallets/{walletId}/withdraw openapi: 3.1.0 info: title: Grain API version: 1.0.0 description: >- Grain's API provides a comprehensive set of endpoints for managing hedging, spot transactions, pricing, and fund movements - enabling seamless integration of FX workflows into your platform. Each API call follows REST conventions, uses secure authentication, and returns standardized responses for consistency across environments. license: name: Creative Commons Attribution 3.0 contact: name: Grain Finance url: https://docs.grainfinance.co email: support@grainfinance.co termsOfService: https://grainfinance.co/terms-of-service/ x-apiClientRegistration: url: https://grainfinance.co/partners servers: - url: https://api.grainfinance.co/v1 description: Grain API security: [] tags: - name: Hedges description: >- Hedge objects represent transactions that lock exchange rates for future dates. A single hedge locks an exchange rate for a future transaction between two currencies. - name: Dual Hedges description: >- A dual hedge mitigates FX risk by automatically generating two linked hedge legs - a customer leg and a supplier leg - both routed through the customer's functional currency. This structure reduces exposure to currency fluctuations for both cash flow and accounting purposes, while allowing independent tracking and reporting of each hedge leg. - name: Customers description: >- Customer objects represent your end customers on the Grain platform. A customer must be created before a hedge or spot transaction can be initiated. - name: Pricing description: >- Pricing endpoints provide access to FX rates for currency pairs that are not being hedged. These endpoints can be used for live rate display or bulk retrieval to support high-volume quoting workflows. - name: Spots description: >- Spot objects represent currency conversions executed for immediate or near-term settlement. - name: Conversions description: >- Conversion objects represent currency conversions executed for immediate or near-term settlement. - name: Wallets description: Endpoints to view balances, manage funding, and perform transfers. paths: /wallets/{walletId}/withdraw: post: tags: - Wallets description: >- Withdraws funds from a wallet to a configured beneficiary. Returns the ID of the created withdrawal fund transfer. operationId: Withdraw parameters: - description: The id of the wallet within the Grain platform. in: path name: walletId required: true schema: $ref: '#/components/schemas/UUID' requestBody: description: The payload required in order to withdraw fund transfers required: true content: application/json: schema: $ref: '#/components/schemas/WithdrawRequestBody' description: The payload required in order to withdraw fund transfers responses: '200': description: Withdraw completed successfully content: application/json: schema: $ref: '#/components/schemas/CreateObjectResponseBody' '400': description: >- The request failed because it is not well-formed or is syntactically incorrect or violates schema. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: The request failed because the resource does not exist. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: Example 1: value: message: The request failed because the resource does not exist. '409': description: The request failed because a business rule constraint was violated. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: Example 1: value: message: >- The request failed because a business rule constraint was violated. '422': description: >- The request failed because it is either semantically incorrect or has failed business validation. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: Example 1: value: message: >- The request failed because it is either semantically incorrect or has failed business validation. security: - api-key: [] components: schemas: UUID: type: string format: uuid description: |- Stringified UUIDv4. See [RFC 4112](https://tools.ietf.org/html/rfc4122) pattern: >- [0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-4[0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12} WithdrawRequestBody: description: >- Withdraw the given amount from your Grain Account to the preconfigured Payment Beneficiary properties: amount: type: number format: double description: The amount of the funds requested to be withdrawn. example: 10000 required: - amount type: object additionalProperties: false CreateObjectResponseBody: description: A response containing the ID of the created object. properties: id: $ref: '#/components/schemas/UUID' description: The id of the created object. example: 1b0ada1e-fa1b-4cfe-a553-01b340c5650e required: - id type: object additionalProperties: false ErrorResponse: description: An API Error properties: message: type: string description: A short explanation of the error. example: Can't perform this action reason: type: string description: A detailed description of the reason for the failure. example: >- Supplied object is in *Cancelled* state, which prevents performing this action required: - message type: object additionalProperties: false securitySchemes: api-key: type: http scheme: basic description: >- Basic authentication using the partner API keys from https://console.grainfinance.co/keys ````