Get a recipient
Retrieve a single recipient (payout destination) you own, by its UUID. The response is the bare recipient object (no { message, data } wrapper).
type—"individual"or"business". Personal name/contact fields are omitted entirely when empty (rather than returned asnull).address— polymorphic: a structured object{ street_name, city, state, postal_code, country }when a city is on file, otherwise a plain string, otherwise omitted. This is the recipient’s own address, distinct from the bank address insideaccount_details.account_type— the rail code (uppercase), e.g.ACH,WIRE,WALLET.account_details— a union whose fields depend onaccount_type. For example:WALLET→{ token, network, address };ACH→{ routing_number, account_number, type, bank_name, bank_address };WIRE→ addsswift_codeand a structuredbank_address.doc_typevalues are normalized to lowercase.metadata— your attached key/value map (defaults to{}).
Errors: a recipient that does not exist or belongs to another client both return 404; a malformed id returns 400.
Authorizations
Access token from POST /auth (the data.access_token value).
API key issued by Kira. Required on every request, including /auth.
Headers
Optional. The date-versioned API version to apply for this request (e.g. 2026-04-14). When sent it always wins, even over your pinned account default. When omitted, the API uses your account's pinned version if set, otherwise a baseline default.
"2026-06-01"
Path Parameters
Recipient UUID.
Response
Success.
The recipient's UUID. Recipients are the naming outlier: this field is recipient_id, not the id used by the user and virtual-account resources — parse it by name.
individual or business. Determines whether the holder is first_name/last_name or company_name.
The payout rail: ACH, WIRE, or WALLET. Mirrors the account.account_type discriminator sent at create time.
Rail-specific bank or wallet details, mirroring the account object sent at create time. Read-after-write caveats: for WIRE, bank_address.state and bank_address.postal_code are silently returned as empty strings even when you sent them; and a holder_name is never stored (the holder is taken from first_name/last_name or company_name).
Creation timestamp. Outlier format: recipients use created_ts (not the ISO-8601 created_at used by user and virtual-account resources) — do not assume it round-trips as ISO 8601.
Last-update timestamp. Like created_ts, this is the recipient-specific *_ts field rather than the updated_at used elsewhere.
Given name (individual recipients). ASCII-normalized on write — accents are transliterated and disallowed characters stripped, so the stored value may differ from what you sent.
Middle name (individual recipients), when provided. ASCII-normalized on write.
Family name (individual recipients). ASCII-normalized on write.
Legal company name (business recipients).
Contact phone for the recipient, when provided.
Contact email for the recipient, when provided.
The recipient's own address (string or structured object). This is distinct from the recipient bank's address, which lives in account_details.bank_address.
Your own key/value string pairs attached to the recipient.