Underwriting, straight from your CRM.
WALT Connect is the W.A.L.T. Partner API. Your CRM or loan-origination system submits the application — borrowers, companies, security and loan — and W.A.L.T. returns an audited, advisory recommendation with risk scores, conditions and the signed PDF report, back on the same record. Nobody re-keys anything.
Status — available on request. Partner API v1 is available in the sandbox on request, and production access is by arrangement. The base URLs and credentials for your integration are provided at onboarding. Within /v1 changes are additive, and every change is recorded in the changelog.
What you can build
- Submit a loan application from the CRM record — individuals, guarantor companies, the security property or properties and the loan details — in one call.
- Attach documents such as the RICS valuation report, then start an assessment: identity, AML/sanctions/PEP, credit, company, valuation and property checks run in parallel, usually within 2 minutes.
- Receive the result through signed webhooks: recommendation, risk and confidence scores, step outcomes, conditions precedent and subsequent, and the PDF report.
- Track borrower actions such as biometric ID verification, and see the assessment update when they complete.
The recommendation is advisory: a qualified underwriter at your firm makes and records the lending decision. Cases created through the API also appear in the W.A.L.T. webapp, marked “Created via CRM”.
Getting started
Three stages, in order. Most teams build and test their connector entirely in the sandbox.
Contract
Agree the WALT Partner API terms and the data processing agreement, and choose the modules your cases need — Credit & Identity Profile, Property Profile or the full Underwriting Suite. Name a technical contact.
Sandbox
We issue sandbox client credentials (OAuth 2.0 client credentials) for a sandbox organisation in WALT’s dev environment. Providers are simulated and test personas choose the outcome. Synthetic data only — never real personal data.
Production
Work through the go-live checklist, register your production webhook endpoint and egress IPs for the allow-list, then receive separate production credentials. Sandbox credentials never work in production.
Environments
| Environment | Base URL | Data |
|---|---|---|
| Sandbox | https://dev-api.underwritinguk.ai/v1(intended public host; your onboarding email gives the base URL to use) | Synthetic only; providers simulated; free |
| Production | https://api.underwritinguk.ai/v1(by arrangement; confirmed when production access is issued) | Live checks; tokens from your plan |
Authentication is OAuth 2.0 client credentials; every create call needs an Idempotency-Key; errors are application/problem+json with a stable code, each documented on its own error page. See Authentication and API conventions.
Resources
- GuideIntegration guideConcepts, the end-to-end flow, webhooks, connector methodology and the go-live checklist.
- ReferenceAPI referenceEvery endpoint, parameter, schema and error, rendered from the OpenAPI document.
- OpenAPI 3.1openapi.jsonImport into Postman, Power Automate, MuleSoft, Boomi or a code generator.
- PostmanPostman collectionThe §6 flow with automatic OAuth token handling and sandbox personas.
- ChangelogWhat changedAdditive changes and deprecations, newest first.
- StatusService statusA public status page (status.underwritinguk.ai) launches with production access.