Verify or reject a document
/lokta-lms/api/v1/sourcing-partners/{partnerId}/documents/{documentId}/verificationVerifies or rejects a partner document.
{"status": "verified"} or {"status": "rejected", "reason": "…"}.
A rejection needs a reason and a verification does not; the same asymmetry as deactivating a partner. Accepting a document is the expected outcome and explains itself; refusing one stops an onboarding, and the partner has to be told what to send instead.
A document cannot be returned to pending. That would erase the fact that somebody looked at it, which is the one thing the verification record exists to preserve.
The checklist's expired still outranks a stored verified, so verifying a document whose valid_to has passed does not make it current.
Path parameters
partnerIdpath · string · requireddocumentIdpath · string · requiredRequest body application/json
statusstring · requiredThe decision. A document cannot be returned to pending.
verified, rejectedreasonstring · optionalRequired when the status is rejected, so the partner knows what to send instead.
Responses
defaultdefault responseEvery request authenticates with HTTP Basic and carries a Tenant-Identifier header. See the conventions for dates, commands, pagination and errors.
Open this operation in the interactive explorer, or read it as Markdown.
This is the API reference for Lokta, the agentic loan servicing platform. Go to lokta.ai