Lender API integrations

Most lenders receive deals as an email package. Some also accept applications directly through their API. When a lender’s API integration is turned on, submitting a deal to that lender sends it into the lender’s system, their decision comes back automatically, and any offers they return land on the deal. Everything else stays the same: the deal moves through the same pipeline stages, and the same notifications fire.

​

Turning it on for a lender

You don’t configure lender APIs yourself. You ask, and NextLevel MCA sets the connection up with the lender for your workspace.

1. When you add a lender, pick it from the list of lenders we track (below) or add a custom one. Lenders on the list show “API integration available on request”.
2. Tick Request API access while creating the lender, or open any lender’s Submission tab and choose Request API access later. Tell us whether you already have API credentials or a partner contact at the lender; it speeds things up.
3. We connect the lender, usually in the lender’s test environment first. The lender shows an amber Dev pill until the lender approves production, so nobody wonders why deals aren’t arriving.
4. Once it’s connected, the lender shows Connected with the integration name, and submissions to that lender go through the API automatically.

You can cancel a request at any time from the same place. Credentials are held by NextLevel MCA, stored encrypted, and never shown in the app.

​

Lenders we track

Credibly, Forward Financing, Kapitus and OnDeck return offers automatically once connected. Fundomate accepts submissions only. The rest have API programs whose depth we confirm as each connection is built. Work with a lender that isn’t listed? Add it as a custom lender and request API access anyway; we’ll look into it.

​

What changes on a deal

• Before you submit, the Submissions tab checks the deal against what that lender requires and lists anything missing in plain words, like “business email” or “average daily balance”. Submit stays disabled until those are filled in.
• After you submit, the lender’s row shows its progress: sent, in review, approved, declined, or funded, along with the lender’s reference number and an Open in funder link.
• Approvals with terms create offers on the deal automatically. If the lender returns several options with identical terms, you get one offer, not duplicates. None is marked primary; that stays your call.
• Errors show the lender’s own message under View error. An error doesn’t always mean the lender didn’t receive the deal, so use Check status before sending again.

Status is refreshed automatically (frequently at first, then less often for up to a week). Check status refreshes it right now.

​

Sending again

To avoid duplicate applications at the lender, Retry only works when the last attempt failed and at least two minutes have passed. The button explains why it is disabled when it is. Credential problems and missing-field errors never retry on their own; fix the cause, then retry.

​

Trying it out

In test workspaces, a built-in Mock funder exercises the whole flow without a real lender. It is configured by NextLevel MCA like any other integration; ask us to enable it on your test workspace if you want to see the submission, status and offer flow end to end before a real lender is connected.

​

For developers

The same actions are available through the API and the MCP tools: api.internal_status values: queued, sent, pending, approved, declined, funded, expired, errored (see error_code and error_message) and stale (no final answer after a week). Full request and response schemas are in the API reference.