Skip to main content
GET
Read a customer

Authorizations

Authorization
string
header
required

Bearer authentication header on the format Bearer <API_KEY>.

Path Parameters

id
string<uuid>
required

Customer's unique identifier.

Query Parameters

includeBalances
boolean

Whether to include balances in the response body.

includeTransactionLimits
boolean

Whether to include transaction limits in the response body. Limits are returned per transaction type (onramp, offramp and transfer).

Response

200 - application/json

Resource successfully retrieved.

id
string<uuid>
read-only

Customer's unique identifier.

Example:

"3c90c3cc-0d44-4b50-8888-8dd25736052a"

type
enum<string>

Customer's type.

Available options:
BUSINESS

Customer's legal name.

Example:

"Lumx S.A"

taxId
string

Customer's tax ID.

Example:

"42.887.120/0001-00"

incorporationDate
string<date>

Customer's incorporation date.

Example:

"2020-01-01"

country
string

Customer's country (ISO 3166-1 alpha-3).

Example:

"BRA"

email
string

Customer's email.

Example:

"hello@lumx.io"

metadata
object

Custom metadata associated with the customer. Returns an empty object if no metadata was provided.

Example:
wallets
object[]

Customer's wallets by blockchain. Only returned when the customer's verification.status is APPROVED.

verification
object

Customer's verification.

requirements
object[]

List of document requirements for KYC/KYB verification.

Example:
additionalInformation
Individual (current questionnaire) · object

Additional information submitted for KYC/KYB verification. Only present after sending additional information. Returns what the customer answered, except phone, the names, address and website: the current questionnaire, or the previous questionnaire for customers created before October 28, 2026.

accounts
object[]

Virtual fiat accounts linked to the customer for receiving payments. Optional—only present when the customer has at least one account. Each entry exposes the account's id and currency.

transactionLimits
object

Customer's transaction limits per transaction type. Only returned when includeTransactionLimits is true. Each transaction type consumes only its own limit: on-ramps count against onramp, off-ramps against offramp and transfers against transfer. A transaction over its type's limit returns 422 with code TRANSACTION_LIMIT_EXCEEDED, and the error message names the transaction type and the limit it would pass.

createdAt
string<date-time>

Creation date and time (UTC).

Example:

"2021-01-01T00:00:00Z"

updatedAt
string<date-time>

Last update date and time (UTC).

Example:

"2021-01-01T00:00:00Z"