Capvant

Push a deal status change

post
https://sandbox.capvant.com/v1/inbound/status/{token}
POST
/inbound/status/{token}

Our deal reference (for example 4F2A9C81D0), the Capvant lead id you received as partnerLeadId, or your own lead id. Send dealRef or id.

Your own lead id: the id you returned when we created the lead (for Salesforce, the 18 or 15 character Lead Id). Also read from leadId, externalId or salesforceId, or from a field you name in the mapping. Send dealRef or id.

A stage (received, contacted, documents_requested, in_underwriting, approved, offer_made, offer_accepted, contracts_sent, contracts_signed, funded, declined, not_proceeding, duplicate), an earlier value (in_review, offer_made, declined, funded), or your CRM stage name. Also read from stage, outcome or StageName when status is absent.

Why the deal ended. Required with declined and not_proceeding unless reason is sent or the stage name is itself the reason. Why a deal ended without funding. Your reasons: insufficient_revenue, time_in_business, credit_score, adverse_history, affordability, existing_debt, negative_balance_days, industry, location_not_served, amount_out_of_range, pricing_not_viable, does_not_meet_criteria, no_business_bank_account, identity_or_fraud, invalid_lead. Either side: statements_insufficient, documents_missing, other (reason_note required). The client’s: merchant_unresponsive, merchant_withdrew, merchant_declined_offer. A duplicate: duplicate_or_existing_customer. After declined or duplicate the request goes on to the other lenders it suits, unless the reason is identity_or_fraud or invalid_lead; after not_proceeding it does not. The client and any referral partner only ever see a neutral sentence for the reason, never your note.

Your own words. Also read from reason_note, decline_reason or note. Required, as the note, when reason_code is other. Kept as the note; when no reason_code is sent, the code is derived from it (text we cannot place is recorded as other).

Funded amount. Required when the stage is funded (also read from funded_amount or data.fundedAmount).

ISO 4217 code of amount. Optional: recorded with the update; the deal keeps its own currency.

data

Optional facts you verified on your side. Stored with the deal so Capvant does not re-collect them.

Product you are offering or funded, e.g. MCA, term_loan, line_of_credit.

Your own stage name, unmapped, for our records.

Commission due to Capvant on this funding.

Send this whenever a deal you received from Capvant changes stage. Find the deal with dealRef (our reference) or id (your own lead id, the one you returned when we created the lead); either is enough. status takes a stage (see LenderStage), one of the earlier values (in_review, offer_made, declined, funded) or your own CRM stage name: common names are understood as they are (Working - Application Out is documents_requested, DNQ is declined for does_not_meet_criteria), and any other name can be mapped to a stage in the Lender Hub. declined and not_proceeding need a reason: reason_code, or free text in reason that we classify (unless your stage name is itself the reason, like DNQ, Not a Lead, Deal Lost or Closed - Not Converted). funded needs amount. Anything else is refused with 400 and a message saying what to send.

Path Parameters

token*string

Your personal inbound secret, part of the URL shown in the Lender Hub.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

application/json

Shell
curl -X POST "https://sandbox.capvant.com/inbound/status/string" \  -H "Content-Type: application/json" \  -d '{    "id": "00Q5g00000AbCdEFGH",    "status": "Working - Application Out",    "data": {      "stage": "Application Out"    }  }'
JSON
{  "ok": true,  "dealRef": "4F2A9C81D0",  "status": "documents_requested"}