Event Types

Every webhook event LendAPI sends, when it is sent, and what the payload contains.

LendAPI sends a JSON POST to your webhook URL each time one of the events below happens to an application. Every event uses the same payload shape. A few events add extra fields with event-specific details.

📘

Accept every event type

Return a 2xx for any event type, including ones you don't use. New event types may be added over time.

Event types

Application progress

EventSent when
application.startedAn applicant starts a new application on your hosted application pages.
application.processingThe application is being processed.
application.reviewThe application is routed to manual review: identity review or credit review.
application.identity_reviewA team member approves the application from identity review.
application.request_docsThe application is waiting for the applicant to upload documents.

Decisions and outcomes

EventSent when
application.approvedThe application is approved.
application.declinedThe application is declined, by a decision or by a team member.
application.bookedThe application is booked.
application.withdrawnThe application is withdrawn.
application.autowithdrawnThe application is withdrawn automatically after a period of inactivity.
application.closedA team member closes the application.

Documents and integrations

EventSent when
application.docreceivedThe applicant or your team uploads a requested document, or your team uploads a signed contract.
application.doc_ai_completedAutomated document processing (DocAI) finishes for an uploaded document.
application.middesk_completedBusiness verification with Middesk finishes. Sent once per application.
manual_credit_pullA team member pulls a credit report manually from the application.

Payload

{
  "api_version": "v1",
  "event_id": "a3d63f54-5b69-46aa-af11-ec4a4797133e",
  "type": "application.booked",
  "product_id": 2,
  "outcome": "Approved",
  "data": {
    "app_id": "92de1f52-15ad-46d4-ae81-08f7a62316c1",
    "tenant_id": "27b61b08-dcba-4baa-8667-8ccc93627c90",
    "current_step_label": "Offer Selection",
    "stage": 5,
    "stage_label": "Booked",
    "additional_data": {
      "utm_source": "partner-site"
    },
    "custom": {
      "variables": {
        "annual_income": 85000,
        "requested_loan_amount": 15000
      }
    }
  }
}

Payload fields

FieldDescription
api_versionAlways v1.
event_idUnique ID for this event. It stays the same when the event is retried, so use it to skip duplicates.
typeThe event type, from the lists above.
product_idID of the application's product. An empty string if the product can't be determined.
outcomeName of the application's final decision outcome. An empty string if there is none.
data.app_idThe application ID. Use it with Get an application to fetch full details.
data.tenant_idYour tenant ID.
data.current_step_labelThe application's current step (Product Studio page). It is the last step the application reached, not the event, so a booked event can still show an earlier step name.
data.stageThe application's stage number. See the stage list below.
data.stage_labelThe stage's display name. Custom stages show your own label.
data.additional_dataQuery parameters passed on the application link or on the API call that created the application. Use it to pass your own reference IDs through. Empty ({}) if there were none.
data.custom.variablesOnly when you chose Webhook Variables for the webhook. Maps each chosen variable to its value for this application.
data.subtenant_idOnly when the application belongs to a sub-tenant.
data.branch_code, data.branch_nameOnly when your workspace uses branches. null when the application isn't assigned to a branch.

The payload tells you what happened and to which application. It isn't the full application record: call Get an application with data.app_id when you need the details.

Stage numbers
stagestage_label
0Processing
1Approved
2Declined
3Document
4Review
5Booked
6Withdrawn
7Doc Received
8Completed
9Default
10Closed
11Pre-Qualify

Extra fields by event

These events add fields at the top level of the payload, next to type and data.

EventExtra fields
application.docreceiveddocument_type: the requested document's name, or Signed Contract. document_name: the uploaded file's name. uploaded_at: upload time (ISO 8601).
application.doc_ai_completedapp_doc_id: ID of the processed document. Some document providers also send doc_ai_task_id.
application.autowithdrawnstatus_type: the status the application was in (processing, doc_requested, or the label of a custom status set up for auto-withdrawal). inactive_days: the number of inactive days that triggered the withdrawal.
application.middesk_completedmiddesk_completed: always true.
manual_credit_pullpull_status and pull_message: the result of the credit pull. bureau_name: the credit bureau.
Example: application.docreceived
{
  "api_version": "v1",
  "event_id": "5e1c9b7a-2d3f-4a6b-8c9d-0e1f2a3b4c5d",
  "type": "application.docreceived",
  "product_id": 2,
  "outcome": "",
  "document_type": "Pay Stub",
  "document_name": "paystub-october.pdf",
  "uploaded_at": "2026-10-28T15:42:10.512000+00:00",
  "data": {
    "app_id": "92de1f52-15ad-46d4-ae81-08f7a62316c1",
    "tenant_id": "27b61b08-dcba-4baa-8667-8ccc93627c90",
    "current_step_label": "Documents",
    "stage": 7,
    "stage_label": "Doc Received",
    "additional_data": {}
  }
}

Next steps

See the Webhooks guide to add a webhook, check the key on your server, and learn how retries work.