> ## Documentation Index > Fetch the complete documentation index at: https://docs.lead.bank/llms.txt > Use this file to discover all available pages before exploring further. # Simulate Advance Funding > Advance a Funding from `processing` to `posted`. Available in Sandbox only. ## OpenAPI ````yaml POST /v2/fundings/{funding_id}/advance openapi: 3.0.1 info: title: Lead Bank description: Lead Bank's APIs version: v1.0 servers: - url: https://api.sandbox.lead.bank - url: https://api.lead.bank security: - bearerAuth: [] tags: - name: ACH - name: Account Number - name: OAuth - name: Events - name: Instant Payments - name: Lending - name: Simulation - name: Internal Transfer - name: Disbursement - name: Entity - name: Wire - name: Originator - name: Funding - name: Receivable Sale - name: Balances - name: Compliance - name: Application - name: User Account - name: Blockchain Payment - name: Core Account - name: Core Balance - name: Core Transaction - name: Event Subscription - name: Receivable - name: User Credit Transaction - name: Files paths: /v2/fundings/{funding_id}/advance: post: tags: - Funding summary: Advance a Funding (Simulation) description: >- Advance a Funding from `processing` to `posted`. Available in Sandbox only. operationId: advance-a-funding-v2 parameters: - name: Idempotency-Key in: header description: Idempotency key required: true schema: type: string maxLength: 255 minLength: 5 - name: funding_id in: path required: true example: funding_0o5Fs0EELR0fUjHjbCnEtdUwQe3 schema: type: string maxLength: 64 description: The ID of the Funding object to advance. responses: '200': description: Successful response content: application/json: schema: type: object properties: {} '400': description: >- The request could not be parsed (`request_malformed`), or the `Idempotency-Key` header is missing (`idempotency_key_missing`). content: application/json: schema: $ref: '#/components/schemas/Error' example: code: idempotency_key_missing message: The Idempotency-Key header is required on this endpoint. '403': description: >- Rejected before the request reached the Funding API. `code` is one of: `authentication_missing` (the request has no credentials), `token_invalid` (the bearer token is expired, invalid, or does not grant the required scope), `source_ip_not_permitted` (the request came from an IP address that is not on your program's allowlist). content: application/json: schema: $ref: '#/components/schemas/Error' example: code: authentication_missing message: >- The request has no authentication credentials. Send your API token in the Authorization header. errors: - code: authentication_missing message: >- The Authorization header is missing. Send your API token as a bearer token. parameters: - Authorization '404': description: >- No v2 Funding with this ID exists, it is not visible to this program, or this endpoint is not available in the current environment. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: object_not_found message: >- No object exists at the requested ID, or it is not visible to this caller. '409': description: >- A concurrent request with the same `Idempotency-Key` is still in flight. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: idempotency_key_in_use message: >- A concurrent request using this Idempotency-Key is still in flight. '422': description: >- The Funding is not in `processing` status (`object_state_conflict`), the Funding ID is malformed (`parameters_invalid`), or this `Idempotency-Key` was used with a different request (`idempotency_request_inconsistent`). content: application/json: schema: $ref: '#/components/schemas/Error' example: code: object_state_conflict message: >- The object is not in the state this request assumed. Fetch its current state before retrying. errors: - code: object_status_unchanged message: >- Funding funding_0o5Fs0EELR0fUjHjbCnEtdUwQe3 is already posted. '429': description: Rate limit exceeded. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: rate_limit_exceeded message: >- You have exceeded the rate limit for this endpoint. Retry with backoff. '500': description: Internal server error. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: internal_server_error message: >- An unexpected error occurred. Contact support with the Request-Id header value. components: schemas: Error: type: object required: - code - message properties: code: $ref: '#/components/schemas/ErrorCode' message: type: string description: >- A human-readable description of the error family. Identical for every occurrence of a given `code`; carries no request-specific detail. example: One or more parameters are invalid. errors: type: array description: >- Zero or more specific errors within this family. Always present for validation errors, one entry per failing field. items: $ref: '#/components/schemas/ErrorItem' ErrorCode: type: string description: >- A snake_case code identifying the error family — the stable, machine-readable value partners branch on, together with the HTTP status. example: parameters_invalid enum: - request_malformed - content_too_large - idempotency_key_missing - authentication_missing - token_invalid - source_ip_not_allowed - url_invalid - object_not_found - method_not_allowed - idempotency_key_in_use - idempotency_request_inconsistent - rate_limit_exceeded - internal_server_error - service_unavailable - endpoint_disabled - gateway_timeout - unclassified - parameters_invalid - related_object_invalid - related_object_not_ready - related_object_conflict - limit_exceeded - client_control_restricted - lead_control_restricted - object_state_conflict - object_modified_concurrently - operation_invalid ErrorItem: type: object required: - code - message properties: code: type: string description: A snake_case code naming the specific error or sub-category. example: required message: type: string description: >- A human-readable description of this specific error, with interpolated values where relevant. example: account_number_id is required. parameters: type: array description: >- The request fields this error implicates, in dot notation for nested fields. Present for validation errors. items: type: string example: - account_number_id securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.