FOR DEVELOPERS
Build evidence review into the workflow—not beside it.
The useful integration is not a button that opens another portal. It is a clear contract for sending review context and receiving structured findings, sources, evidence locations, and status back to the lender’s system.
API OUTPUT IS REVIEW SUPPORT
LendlyX returns verification findings and evidence context. The consuming application must preserve lender authorization, policy, exception handling, and final decision controls.
API REVIEW LX-1048
Structured output with human context
Review request
Loan and evidence context received
VERIFIED
Evidence references
Purpose-built checks completed
SECOND REVIEW
Finding object
Reasons and source references returned
PASS
Disposition
Lender action remains in the host system
NOT REQUESTED
Design the contract around the reviewer’s next question
A stable integration should make the relationship between the loan, evidence, finding, source, and lender disposition explicit.
01
Review request
INPUT Loan identifier, analysis type, and review context
TEST Required context and authorization boundary
RETURN Accepted request and tracking reference
02
Evidence references
INPUT Documents, data, media, and source metadata
TEST Source association and file integrity
RETURN Connected evidence set
03
Finding object
INPUT Reason code, status, source, and evidence location
TEST Schema validity and evidence traceability
RETURN Structured reason-coded finding
04
Audit event
INPUT Reviewer action, timestamp, and disposition context
TEST Record association and immutable history
RETURN Review history for the lender record
ILLUSTRATIVE FINDING OBJECT
FINDING-014 · SOURCE_VARIANCE
SECOND REVIEW
WHAT CHANGED
A visible document value differs from its corresponding source-data value.
WHY IT MATTERS
The host workflow needs a machine-readable reason and enough human context to route review correctly.
EVIDENCE
The finding carries source references, evidence locations, analysis context, and current status.
REVIEWER ACTION
Present the evidence to an authorized reviewer and record the lender’s disposition.
A BETTER API CONTRACT
A status code is not an explanation.
The integration should preserve what changed, why it matters, where the evidence lives, and which action belongs to the lender.
→ What changed?
→ Why does it matter?
→ Which source object supports the finding?
→ What should the reviewer do next?
From request to review record
Keep the integration idempotent, traceable, and explicit about the boundary between analysis and lender decisioning.
01
Create the request
Send the loan identifier, analysis type, and review context.
02
Attach the evidence
Connect documents, data, media, and source references.
03
Receive structured findings
Handle status, reasons, sources, and evidence locations together.
04
Write back the disposition
Persist the lender’s action and review history in the system of record.
Start with one workflow and one representative file. Then design the contract around the evidence.
See LendlyX in your workflow →