LElead
Compliance

Update an application

Changed on

Updates properties on an existing application.

Uses JSON Merge Patch semantics (RFC 7396): omitted fields are unchanged, explicit values overwrite, nested objects merge recursively.

Note: Entity relationships are set when the application is created and cannot be modified afterward. There is no endpoint for adding or removing entity relationships on an existing application; GET /v0/applications/{id}/entity_relationships is read-only.

Idempotency

The Idempotency-Key header is required.

patch/v0/applications/{id}

Request

  • Base URL
    https://api.sandbox.lead.bank
  • URL
    https://api.sandbox.lead.bank/v0/applications/{id}
  • Auth
    HTTP bearer

Path parameters

idstring required

Unique identifier for the application. Prefixed with application_.

Example:application_xyz123

Application ID

Headers

Idempotency-Keystring required

Unique key to ensure idempotent requests

Request body

status'approved' | 'declined' | 'canceled'

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

metadataobject

Arbitrary metadata associated with the application

Example request

{
  "details": {
    "product_name": "Growth Business Credit Line",
    "credit": {
      "underwriting_grade": "99",
      "limit": 5000000,
      "max_limit": 10000000
    }
  },
  "documents": [
    {
      "document_id": "document_2N5Hk8xYmQpL9rBvC3jD",
      "version": "v1"
    }
  ]
}

Response

Application updated successfully.

idstring

Unique identifier for the application. Prefixed with application_.

client_application_idstring

Client-provided identifier for the application. Optional: present only for applications created via file upload, and omitted for applications created through the API, which are identified solely by their server-generated ID.

created_atstring date-time

Lead server-generated ISO 8601 timestamp when the application was created.

updated_atstring date-time

Lead server-generated ISO 8601 timestamp when the application was last updated.

status'approved' | 'declined' | 'canceled'

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

metadataobject

Arbitrary metadata associated with the application

Example response

{
  "id": "application_xyz123",
  "entities": {
    "account_holder_type": "commercial",
    "account_holders": [
      "entity_xyz123"
    ],
    "authorized_signers": [
      "entity_xyz123"
    ]
  },
  "details": {
    "product_name": "Growth Business Credit Line",
    "credit": {
      "underwriting_grade": "99",
      "limit": 5000000,
      "max_limit": 10000000
    }
  },
  "documents": [
    {
      "document_id": "document_2N5Hk8xYmQpL9rBvC3jD",
      "version": "v1"
    }
  ]
}

Changes

  • 2c659854496eRevision changes
    • warning

      added the new autopay_authorization enum value to the // response property for the response status

    • warning

      added the new cardholder_agreement enum value to the // response property for the response status

    • warning

      added the new deposit_agreement enum value to the // response property for the response status

    • warning

      added the new periodic_statement enum value to the // response property for the response status

    • info

      added the new autopay_authorization enum value to the request property ///

    • info

      added the new autopay_authorization enum value to the request property //

    • info

      added the new cardholder_agreement enum value to the request property ///

    • info

      added the new cardholder_agreement enum value to the request property //

    • info

      added the new deposit_agreement enum value to the request property ///

    • info

      added the new deposit_agreement enum value to the request property //

    • info

      added the new periodic_statement enum value to the request property ///

    • info

      added the new periodic_statement enum value to the request property //