Embed equipment financing into your website, checkout or point-of-sale system. Submit applications, get automated underwriting decisions, manage documents and retrieve signed application packages over a simple REST API.
The API is organized around REST. All requests and responses are JSON (except binary PDF downloads). The base URL is:
The core flow is bi-directional:
Authenticate every request with your partner API key as a bearer token. Request a key from your seller dashboard after signing up.
Keep your secret key server-side. Never expose it in client-side code. Keys can be rotated or revoked at any time.
Submit an application and receive a decision in one call:
/applicationsSubmit an application and receive an automated underwriting decision.
Returns one of three outcomes:
Credit scores and bureau data are never returned to partners.
/applications/{id}Retrieve full application status, the latest decision, current offers, required/uploaded documents, and the status timeline.
/applications/{id}/documentsList documents required by underwriting and documents already uploaded.
/applications/{id}/documentsUpload a document (JSON base64 or multipart form-data). Fulfills an open request when request_id is supplied.
/applications/{id}/pdfDownload the completed, e-signed application PDF (signature, IP, timestamp) for your lender package. Returns application/pdf.
/enrichPrefill business data from a website, name, or EIN (powered by Enigma + SEC EDGAR).
After the automated decision, an application moves through review, contracting and funding. Poll GET /applications/{id} (every few minutes is plenty) and compare status and updated_at. Every response uses one of these statuses:
submitted — received, not yet decidedin_review — with our credit teamdocuments_required — upload the documents in required_documentsapproved — offers are available to the borrowerdeclined — see decision.reasonscontracting — contracts sent, signed or being verifiedfunded — the deal has fundedclosed — withdrawn, or approved but not taken upWebhook notifications are planned; until then, polling is the supported way to follow an application.
Errors return JSON with a machine-readable error code and a human-readable message:
200 / 201 — success400 — request body is not valid JSON401 — missing or invalid API key404 — application not found (or not yours)422 — validation error (missing fields are listed in a missing array)429 — rate limited (120 requests per minute per key); wait the seconds in the Retry-After header503 — temporary server configuration issueSign up for a seller partner account to get your API keys and start embedding financing today.
Get API access