Introduction to the Lender API

The Capvant Lender API gives funding partners programmatic access to the same deal flow the referral emails and the Lender Hub carry: matched, consented SME funding referrals with a unique reference per deal.

Choose your integration

Everything is built around the deal. A deal is one funding request from one verified business, routed to your lane because it matched your published criteria. Each deal keeps a single reference (for example CV93A41205) across every channel, whether your team works the referral email, the Hub, or this API.

What you can do

refstringThe deal reference. It appears in every URL, email and webhook about this deal.always

statusenumThe marketplace state of the deal itself. We move it.always

lender_statusenumYour own position on the deal. Only you move it.always

channelobjectThe brand the client applied through, with its name and domain. Address the client by it.always

businessobjectRegistered name, company number, legal form and status.always

contactobjectName, email and phone for the person who applied.always

marketobjectOne object per country, under a discriminator on market.country. The keys that country carries, and nothing else.always

registryobjectWhat the public register answered, with the time it was read, or a status saying why it did not.can be null

monthly_revenuenumberFrom the statements once they are parsed, from the applicant band before that. The matching _basis field says which.always

statementsobjectProvider, months covered, average inflow and outflow.after documents

documentsarrayEvery file with its type, size, upload time and a signed link.after documents

consentobjectWhen the client agreed and to what text, including whether it covers a soft credit search.always

• Pull your pipeline: list and retrieve every deal referred to you, with business, contact and financial details.
• Report statuses: mark a deal in review, offer made, declined or funded. Statuses route more flow to lanes that convert.
• Submit offers: push indicative or firm terms straight into the client's comparison view.
• Message clients: read and send messages on a deal, including secure document-upload requests.
• Request typed documents: ask for a specific item (a debt schedule, management accounts, an aged debtors report...) and track it through requested, uploaded and forwarded.
• Receive webhooks: signed notifications for new deals, status changes and client messages.

Two ways to receive deal flow

Lenders can integrate either way, and most use both over time:

• Pull (self-serve): call GET /deals with your own API key whenever you want, or register a webhook and never poll. This is what the rest of this reference documents.
• Push (on request): we submit complete applications directly to an endpoint you provide, instead of you pulling from us. Available for lanes that want deals delivered rather than fetched; contact partnerships@capvant.com to set it up.

The Partner API on the other side is push-only by nature: partners push referrals to Capvant, not the reverse. See Partner API overview.

Design notes

• REST over HTTPS, JSON in and out, snake_case fields.
• All data is scoped to your organisation. A key can never see another lender's deals.
• The API is additive to email and the Hub, not a replacement. A one-word email reply and a POST /deals/{ref}/status land in exactly the same place.