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 application. See Idempotency.

Maximum string length: 255

Body

application/json

Request body for POST /v2/applications. The application is created in its final status.

client_application_id and legacy_documents are read only. Lead ignores them, and any other field this endpoint does not define, if sent.

status
enum<string>
required

Terminal state of the application. Possible values: approved, declined, canceled.

Available options:
approved,
declined,
canceled
product_name
string
required

Your internal product name. It tells Lead which product the application opens a user account for if approved. Use a stable name.

Example:

"Growth Business Credit Line"

entities
object
required

The entities on the application. Each must already exist. Each relationship type takes up to 20 entities, and no entity can appear twice in one type. The account holders must be all consumer (individuals) or all commercial (businesses or sole proprietorships).

On approved applications only, each entity must be eligible for its relationship type, and a commercial application needs at least one authorized signer. Your program can also require credit data on each account holder's and authorized signer's entity for approved applications; your Technical Account Manager can tell you whether yours does.

account_holder_type is derived by Lead and response only, so Lead ignores it if sent. Entities cannot change after creation.

details
object
required

Underwriting and adverse action notice details.

decision
object
required

When and why the underwriting decision was made.

documents
object[]
required

Compliance documents, each referencing a file you uploaded with POST /v2/files. Lead takes the document type from the file, which must be a compliance document type. Send [] when you have no documents yet.

  • Each file_id must exist, belong to your program, and appear at most once.
  • One file can back many applications.
metadata
object

Key-value pairs for your own use.

Response

Application created.

An application, your report of an underwriting decision. Applications created on v0 are returned in this shape.

id
string
required

Unique identifier for the application. Prefixed with application_.

Pattern: ^application_\w+$
Example:

"application_xyz123"

status
enum<string>
required

The application's status. Applications created through the API are always approved, declined, or canceled, the statuses POST accepts.

submitted and under_review appear only on applications you reported in an Application file before a decision was made. They are read only: POST does not accept them, and a PATCH that includes status leaves it unchanged.

Available options:
approved,
declined,
canceled,
submitted,
under_review
Example:

"approved"

product_name
string
required

Your internal product name.

Example:

"Growth Business Credit Line"

entities
object
required

The entities on the application. Authorized users are not returned here; list them with GET /v2/applications/{id}/entity_relationships.

details
object
required

Underwriting and adverse action notice details.

documents
object[]
required

Compliance documents linked on v2, each referencing an uploaded file. Always an array.

created_at
string<date-time>
required

When the application was created. RFC 3339, UTC.

Example:

"2026-05-14T15:59:30Z"

updated_at
string<date-time>
required

When the application was last updated. RFC 3339, UTC.

Example:

"2026-05-14T15:59:30Z"

client_application_id
string
read-only

Your ID for applications you reported in an Application file. Lead omits it for applications created through the API.

Example:

"APP-2024-001"

decision
object

When and why the underwriting decision was made. Absent when status is submitted or under_review.

legacy_documents
object[]
read-only

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

metadata
object

Key-value pairs for your own use.