Skip to main content
POST

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Idempotency-Key
string
required

A unique key for this request, up to 255 characters. Retrying with the same key and body returns the original response without creating a second user account. See Idempotency.

Maximum string length: 255

Body

application/json

Request body for creating a new user account

requested_features
enum<string>[]
required

The features the user account should be granted. The feature must be pre-approved for your program. Learn more about features here.

A feature of the user account

Available options:
deposit,
credit_with_underwriting,
credit_without_underwriting
entities
object
required

Entity relationships for the user account (POST request only). Maximum 20 entities per relationship type. Cannot mix individual and business/sole_prop entities in account_holders. Authorized signers required for business/sole_prop account holders.

product_name
string
required

Partner's name for their product

product_config_id
string
required

Identifies the product configuration set up for your program. Provided to you by your Lead Technical Account Manager. Cannot be changed once set.

Pattern: ^product_config_\w+$
Example:

"product_config_xyz123"

documents
object[]
required

Compliance documents linked to the user account. Each entry references a file uploaded with the Files API. Send [] when there are none to link yet.

application_id
string

Unique identifier for the application. Prefixed with application_.

Pattern: ^application_\w+$
Example:

"application_xyz123"

balance_sheet_model
enum<string> | null

How Lead carries the user account's credit on its balance sheet. Required whenever requested_features includes a credit feature. Cannot be changed once set. Learn more about balance sheet model here.

Available options:
held_for_investment,
held_for_sale
details
object

Additional details for the user account

metadata
object

A set of key-value pairs that can be used to store additional information related to this object.

Response

User account created successfully.

A user account object

id
string
required

The ID of the User Account object.

Pattern: ^user_account_\w+$
Example:

"user_account_xyz123"

status
enum<string>
required

Current state of the user account

Available options:
active,
inactive,
closed
status_reason
enum<string>
required

Machine-readable reason for the current status

Available options:
client_closed,
entity_closed,
frozen,
dormant,
active,
paid_off,
charged_off,
canceled,
other
features
enum<string>[]
required

Features granted to the user account.

A feature of the user account

Available options:
deposit,
credit_with_underwriting,
credit_without_underwriting
entities
object
required
read-only

Entity relationships associated with the user account (response only)

details
object
required
read-only

Core details of the user account

product_name
string
required

Partner's name for their product

documents
object[]
required

Compliance documents linked to the user account. Each entry references a file uploaded with the Files API.

metadata
object
required

A set of key-value pairs that can be used to store additional information related to this object.

created_at
string<date-time>
required
read-only

Creation timestamp

updated_at
string<date-time>
required
read-only

Last update timestamp

application_id
string

Unique identifier for the application. Prefixed with application_.

Pattern: ^application_\w+$
Example:

"application_xyz123"

legacy_documents
object[]
read-only

Document entries created on v0 User Accounts, returned exactly as sent. Read only: ignored if included on a POST or PATCH.

client_account_id
string
read-only

The identifier you assigned in an Account file. Present only on user accounts created through file upload. Omitted on user accounts created through the API, which are identified only by id.

balance_sheet_model
enum<string> | null

How Lead carries the user account's credit on its balance sheet.

Available options:
held_for_investment,
held_for_sale
product_config_id
string | null

The id of the product configuration the user account was created under. null only on user accounts created before product config ids existed.

Pattern: ^product_config_\w+$
Example:

"product_config_xyz123"

closed_at
string<date-time> | null
read-only

Timestamp when the user account was closed. Updated by /close endpoint.