Webhooks

Webhooks notify your systems when events happen in LendAPI — for example, when an application is submitted or a decision is made. They let you connect application activity to your own systems (a loan origination system, a CRM, an internal alerting tool) without you having to poll LendAPI for changes.

Webhooks are managed from the Webhook tab inside your tenant’s Settings area, alongside Profile, Workspace, Configuration, Security, Users, and API settings.

---

How it works

You create a webhook endpoint, give it a name, point it at a URL you control, and choose which events should trigger a delivery. When one of those events occurs for your tenant, LendAPI sends an HTTP POST to your URL with a payload describing the event.

Worked example

A tenant, Meridian Credit Union, wants its loan origination system to know the moment an underwriter makes a decision on a personal loan application, so it can update the borrower’s status without manual re-entry.

1. An operations admin at Meridian goes to Settings > Webhook.
2. They click Create and name the webhook “LOS decision sync.”
3. They enter the HTTPS URL of their loan origination system’s intake endpoint.
4. They select the application.decision event (and, since they also want early visibility into new volume, application.submitted).
5. They save. The webhook is created active by default, so deliveries start immediately.
6. Later that day, an underwriter approves a $22,000 personal loan application from an applicant with a 705 FICO score. LendAPI sends a POST to Meridian’s endpoint describing the decision event. The LOS updates the application’s status on receipt.

Use case

A subprime auto lender processes several thousand applications a day across multiple dealer partners. Instead of having staff check LendAPI for new decisions, the lender configures a webhook pointed at its internal dashboard so that every application.decision event pushes an update automatically, keeping dealer-facing status pages current without manual polling.

---

Viewing webhooks

1. Go to Settings and open the Webhook tab.
2. The list shows each webhook’s name, URL, events, status (active/inactive), created date, and last triggered time (if available).

---

Creating a webhook

1. On the Webhook tab, click Create (or Add webhook).
2. Enter a name you’ll recognize later, such as “Production events.”
3. Enter the URL of your endpoint. It must be HTTPS in production.
4. Select the events you want to receive, such as application.submitted or application.decision.
5. Save. The webhook is created active unless you turn it off.

Your endpoint receives HTTP POST requests with a payload whenever a selected event occurs. Build your endpoint to handle retries and duplicate deliveries.

---

Editing a webhook

Open the webhook from the list and change its name, URL, or event selection. Save your changes. Past deliveries aren’t re-sent — only events that occur after you save use the new configuration.

---

Activating and deactivating

• Deactivate a webhook to stop deliveries without deleting it — for example, while you’re fixing a broken endpoint.
• Activate it again to resume deliveries.

---

Deleting a webhook

Delete a webhook when you no longer need it. LendAPI stops sending events to that URL immediately.

---

Best practices

• Use a descriptive name for each webhook (for example, “LOS decision sync” rather than “Webhook 1”) so you can tell them apart in the list.
• Deactivate a webhook instead of deleting it while you troubleshoot your endpoint, so you don’t lose the event selection you configured.
• Select only the events you actually consume. This keeps your endpoint’s traffic and your own logs easier to reason about.
• Design your endpoint to tolerate duplicate deliveries and retries rather than assuming exactly-once delivery.

---

Unclear or not covered here

• Exact payload structure and fields for each event type.
• Retry schedule, timeout, or failure-handling behavior on LendAPI’s side.
• Whether inactive webhooks queue events for later delivery or drop them.