--- title: "Retrieve a Receivable" method: GET path: "/v2/receivables/{receivable_id}" tags: ["Receivable"] --- # Retrieve a Receivable `GET /v2/receivables/{receivable_id}` ## Request - Base URL: `https://api.sandbox.lead.bank` - URL: `https://api.sandbox.lead.bank/v2/receivables/{receivable_id}` - Auth: HTTP bearer Retrieve a Receivable by its ID. ## Path parameters - `receivable_id` string, required ## Response `200` A Receivable object. - Receivable - `id` string, required: Unique ID of the Receivable object. - `currency_code` 'USD', required: A three-letter currency code as defined in ISO 4217. - `type` 'card_network_settlement' | 'user_credit_balance', required: The origin of the event that created the receivable. This value does not change after the receivable is created. - `card_network_settlement`: the receivable was created from a card network settlement. `card_network_settlement_details` is present. - `user_credit_balance`: the receivable was created from a User Credit Transaction drawn on a User Credit Balance. `user_credit_balance_details` is present. - `held_for` 'sale', required: Whether the receivable is meant for sale or to stay on Lead's balance sheet. - `sale`: the receivable is held for sale. - `investment`: the receivable is held for investment on Lead's balance sheet. A receivable can move from `investment` to `sale`. - `origination_date` string, date: The date the receivable originated. For a card network settlement this is the settlement date; for other sources it is the date the source object was created. When receivable data arrives late, this is the date the receivable should have originated on, while `created_at` is when the Receivable object was created. Omitted when the receivable is held for investment. - `amount` integer, required: The overall amount of the receivable, in minor units. Equal to the sum of `amount_breakdown.principal`, `amount_breakdown.interest`, and `amount_breakdown.fees`. - For receivables held for sale, the amount is locked at the loan amount to be sold when the receivable is reclassified for sale. - For receivables held for investment, the amount is live: it grows with originations and decreases with payments and charge-offs. - `amount_breakdown` ReceivableAmountBreakdown, required: The principal, interest, and fees that make up the receivable's `amount`, in minor units, along with the interest rate applied. - `principal` integer, required: The principal amount, in minor units. - `interest` integer, required: The interest amount, in minor units. `0` when the receivable's source carries no interest. - `interest_rate` number, double, nullable, required: The annual interest rate applied, as a decimal percent (for example, `9.99` means 9.99%). This is a rate, not an amount. Null when the receivable's source carries no rate, as with card network settlements. - `fees` integer, required: The fee amount, in minor units. `0` when the receivable's source carries no fees. - `receivable_sale_details` ReceivableSaleDetails, required: The sale this receivable is part of. Each field is set at a different point in the receivable's lifecycle, so either may be null. - `receivable_sale_id` string, required: Unique ID of the Receivable Sale object. - `request_date` string, date, nullable, required: The business day the receivable is requested for sale. Once the receivable is grouped into a sale, this is the sale's `request_date`. Null until it is set. - `card_network_settlement_details` ReceivableCardNetworkSettlementDetails: Identifies the card network settlement the receivable was created from. - `settlement_reporting_id` string, required: The program's per-network reporting ID for the settlement. - `card_network` 'visa' | 'mastercard' | 'pulse' | 'accel' | 'maestro' | 'tabapay' | 'amex' | 'star' | 'interlink', required: The card network the settlement came from. - `settlement_date` string, date, required: The network settlement date. - `user_credit_balance_details` ReceivableUserCreditBalanceDetails: Identifies the User Credit Balance and User Credit Transaction the receivable was created from. - `user_credit_balance_id` string, required: ID of the User Credit Balance the receivable is drawn from. - `user_credit_transaction_id` string, required: ID of the User Credit Transaction that drew on the User Credit Balance and created the receivable. - `created_at` string, date-time, required: The ISO-8601 timestamp at which the Receivable object was created. - `updated_at` string, date-time, required: The ISO-8601 timestamp at which any field on the Receivable object was last updated. ## Other responses - `400`: The request URL could not be parsed. - `403`: Rejected before the request reached the Receivable 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 with this ID exists, or it is not visible to this program. - `422`: The Receivable ID in the path is not a well-formed Receivable 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/receivables/:receivable_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)