Request a state change
/lokta-lms/api/v1/sourcing-partners/{partnerId}/state-change-requestsRequests a change of state for a sourcing partner, with a reason.
{"requested_state": "on_hold" | "deactivated" | "active", "reason": "…"}. A reason is required: the checker decides on it and the trail keeps it.
One open request per partner: a second is 409 sourcing/state_change_already_pending. Requesting active fails fast if the partner cannot be activated (external id, terms), and the same gate re-runs authoritatively at approval, because the world changes between request and decision.
Path parameters
partnerIdpath · string · requiredHeader parameters
Idempotency-Keyheader · string · optionalPer-intent key
Request body application/json
requested_statestring · requiredThe state being asked for.
on_hold, deactivated, activereasonstring · requiredRequired. The checker decides on it and the trail keeps it.
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