API & LOS
Start a report from your loan system.
Your team types a case ID. LegiScore pulls the borrower, property and documents from your LOS, and sends every status change back by webhook.
LOS case LOS-5521
Connected- Case ID receivedTyped by the credit teamReceived
- Data and documents pulledFrom your loan systemPulled
- Report startedPre-filled, no re-keyingRunning
- Status returned to LOSWhen the report completesQueued
Example
Side by side
Manual Data Entry vs One Case ID
Without Connectors
- Starting a report. Re-key every field from the LOS by hand
- Documents. Documents emailed around and re-uploaded
- Setup. Each analyst configures their own workflow
- Credentials. Logins shared informally and unmanaged
- Consistency. Every report starts from a blank form
Inbound Connectors
One Case ID, A Pre-Filled Report
Configure the connector once. After that, every analyst starts a report from a single LOS case ID.
Start from a LOS case ID
Credit teams enter their loan origination case ID on the new-report screen. That is all it takes to begin.
Your LOS
Case ID
HL-2026-04127
LegiScore, pre-filled
- Borrower and co-applicant names
- Property address and survey number
- 6 documents from the loan file
Webhooks back to your LOS
- report.startedReport started200 OK
- report.paused.missing_documentsReport paused — missing documents200 OK
- report.completedFinal report ready200 OK
10 events in all, from new asset to report completed.
Example
Server-side data fetch
LegiScore pulls case data and documents from your loan origination system on the server, no manual export.
- Start from a LOS case IDOn
- Server-side data fetchIn focus
LegiScore pulls case data and documents from your loan origination system on the server, no manual export.
- Auto-filled fields and documentsOn
- Guided Test-then-map setupOn
- Credentials encrypted at restOn
- Per-org brandingOn
Example
Auto-filled fields and documents
Form fields, custom fields, and source documents fill themselves from the case so the report starts ready.
Guided Test-then-map setup
An admin configures the connector once with a guided flow: test the fetch, then map fields to your report.
Credentials encrypted at rest
Connector credentials are encrypted and never re-keyed by analysts. Configure once, secure by default.
Per-org branding
The connector and report surface carry your institution’s branding for every team that uses them.
Organization Accounts
Built for Teams, Not Seats
Connectors sit on top of full organization accounts, shared credits, roles, branches, and org-default configurations.
Shared credit pools
One organization balance funds every branch and analyst, no per-seat top-ups.
- Shared credit poolsIn focus
One organization balance funds every branch and analyst, no per-seat top-ups.
- Roles and branchesOn
- Org-default report configsOn
- Org-wide, not per-analystOn
Example
Roles and branches
Role-based access and branch structure mirror how your institution is organized.
- Shared credit poolsOn
- Roles and branchesIn focus
Role-based access and branch structure mirror how your institution is organized.
- Org-default report configsOn
- Org-wide, not per-analystOn
Example
Org-default report configs
Set default report configurations once so every report your team runs starts from the same standard.
Org-wide, not per-analyst
Configure connectors and policy at the organization level instead of repeating setup for each user.
1
case ID typed to start a pre-filled report
10
webhook events back to your system
Encrypted
LOS credentials are stored encrypted, set up once per organisation
Questions
Your questions, answered.
How does a credit analyst start a report from our LOS?
Who sets up the connector and how?
How are our credentials and data protected?
Does this work for a whole team and not just one user?
Keep going
The rest of the platform
The pipeline
Scale
Platform