---
title: "Retrieve a Funding"
method: GET
path: "/v2/fundings/{funding_id}"
tags: ["Funding"]
---

# Retrieve a Funding

`GET /v2/fundings/{funding_id}`

## Request

- Base URL: `https://api.sandbox.lead.bank`
- URL: `https://api.sandbox.lead.bank/v2/fundings/{funding_id}`
- Auth: HTTP bearer

Retrieve a Funding by its ID. Fundings created through `/v0/fundings` are not visible on this endpoint.

## Path parameters

- `funding_id` string, required

## Response `200`

A Funding object.

- FundingV2
  - `id` string, required: Unique ID of the Funding object.
  - `user_credit_balance_id` string, required: ID of the User Credit Balance this funding draws against.
  - `account_number_id` string, required: The ID of the Lead Bank Account Number object.
  - `currency_code` 'USD', required: A three-letter currency code as defined in ISO 4217.
  - `amount` integer, required: The total principal disbursed, in minor units.
  - `metadata` object: Additional metadata associated with the funding.
  - `core_transaction_id` string, nullable, required: ID of the Core Transaction that credited the destination balance. `null` until the funding is `posted`.
  - `status` 'processing' | 'posted' | 'rejected', required: The current status of the Funding object.
  - `rejection` FundingRejection, required: Object containing information relevant for cases where the Funding object is in a rejected status. When the object is not in a rejected status, fields will still be present with empty strings.
    - `reason` 'internal_error': The rejection code that indicates the type of rejection. Note that Lead may introduce additional enums in the future; partner integrations should be ready to handle them as non-breaking changes.
    - `details` string: Additional info about the rejection. Reserved for future use.
  - `created_at` string, date-time, required: The ISO-8601 timestamp at which the Funding object was created.
  - `updated_at` string, date-time, required: The ISO-8601 timestamp at which the Funding object was last updated.

## Other responses

- `400`: The request URL could not be parsed.
- `403`: 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).
- `404`: No v2 Funding with this ID exists, or it is not visible to this program.
- `422`: The Funding ID in the path is not a well-formed Funding ID.
- `429`: Rate limit exceeded.
- `500`: Internal server error.
- `504`: An upstream system did not respond in time. Retry with backoff.

## Changes

- **2026-11-03** `2c659854496e`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/lead/apis/lead-bank/changes/v2/fundings/:funding_id/get.md)

---

[API](https://skmtc.dev/lead/apis/lead-bank.md) - [All operations](https://skmtc.dev/lead/apis/lead-bank/llms.txt) - [OpenAPI document](https://skmtc.dev/lead/apis/lead-bank/revisions/2c659854496e?raw)