---
title: "Retrieve a Receivable Sale"
method: GET
path: "/v2/receivable_sales/{receivable_sale_id}"
tags: ["Receivable Sale"]
---

# Retrieve a Receivable Sale

`GET /v2/receivable_sales/{receivable_sale_id}`

## Request

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

Retrieve a Receivable Sale by its ID, including its rollup totals. To list the Receivables in it, use `GET /v2/receivables?receivable_sale_id={receivable_sale_id}`.

## Path parameters

- `receivable_sale_id` string, required

## Response `200`

A Receivable Sale object.

- ReceivableSale: A receivable sale is the aggregate of a program's eligible receivables for a single business day, which you purchase as a single unit.
  - `id` string, required: Unique ID of the Receivable Sale object.
  - `status` 'created' | 'settled' | 'failed', required: The status of the receivable sale. - `created`: the sale has been created and its member receivables and amounts are frozen. - `settled`: the `purchase_amount` has been debited from your account. `core_transaction_id` and `settled_at` are set. - `failed`: the sale could not be settled because your account has insufficient funds or is closed. `failure` describes why. Any other problem leaves the sale `created`.
  - `request_date` string, date, required: The business day being sold. This may be earlier than `created_at` when a sale is generated for a past business day.
  - `currency_code` 'USD', required: A three-letter currency code as defined in ISO 4217.
  - `purchase_amount` integer, required: The total amount you pay for the sale, in minor units, debited from your account as a single entry when the sale settles. Equal to the sum of the member receivables' amounts, frozen when the sale is created, and to the sum of the components in `purchase_amount_breakdown`.
  - `purchase_amount_breakdown` ReceivableSalePurchaseAmountBreakdown, required: The components that make up the sale's `purchase_amount`, in minor units. The components always sum to `purchase_amount`. This object is an open map: Lead may add new components (for example, a premium) in the future without a version change. Each component is a signed integer, so a component that reduces the amount due is negative. Sum every key present rather than only the ones listed here.
    - `principal` integer, required: The sum of the member receivables' outstanding principal, in minor units, frozen when the sale is created.
    - `interest` integer, required: The sum of the member receivables' outstanding borrower interest, in minor units, frozen when the sale is created.
    - `fees` integer, required: The sum of the member receivables' outstanding borrower fees, in minor units, frozen when the sale is created.
  - `receivables_count` integer, required: The number of receivables in the sale. List them with `GET /v2/receivables?receivable_sale_id={id}`.
  - `core_transaction_id` string, required
  - `failure` ReceivableSaleFailure: Why a receivable sale failed to settle.
    - `reason` 'non_sufficient_funds' | 'account_closed', required: Why the sale could not be settled. - `non_sufficient_funds`: your account has insufficient funds for `purchase_amount`. - `account_closed`: your account is closed.
    - `details` string, required: A description of the failure and what to do next.
  - `created_at` string, date-time, required: The ISO-8601 timestamp at which the Receivable Sale object was created.
  - `settled_at` string, date-time, nullable, required: The ISO-8601 timestamp at which the sale settled and `purchase_amount` was debited. Null until the sale is `settled`.
  - `updated_at` string, date-time, required: The ISO-8601 timestamp at which the Receivable Sale object was last updated.

## Other responses

- `400`: The request URL could not be parsed.
- `403`: Rejected before the request reached the Receivable Sale 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 Receivable Sale with this ID exists, or it is not visible to this program.
- `422`: The Receivable Sale ID in the path is not a well-formed Receivable Sale 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/receivable_sales/:receivable_sale_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)