Create a sourcing partner
/lokta-lms/api/v1/sourcing-partnersCreates a sourcing partner in the pending state.
Creates the partner in pending. It cannot be attributed until it is activated, and activation requires an agreement on file; onboarding is a sequence, not a form.
details and contacts may ride this call so onboarding is one request; afterwards each is maintained through its own sub-resource. If contacts are supplied and none is marked primary, the first becomes primary, because every screen downstream assumes a partner has a point of contact.
Requires an Idempotency-Key. Reusing a key with a different body is a 409 rather than a silent replay of the first response.
When to use it
This starts onboarding. The partner is created as pending. Add an agreement and then activate it, because a partner cannot be attributed a loan until it is active.
Worth knowing
- Send an Idempotency-Key header. Reusing a key with a different body returns 409.
Header parameters
Idempotency-Keyheader · string · optionalPer-intent key; persist it before sending and reuse it on retry
Request body application/json
namestring · optionalPlaceholder name, to be confirmed. The partner's name.
external_idstring · optionalPlaceholder name, to be confirmed. The partner's external id.
partner_typestring · optionalPlaceholder name, to be confirmed. A partner type code from the reference data.
detailsobject · optionalThe partner's details. May ride this call so onboarding is one request.
contactsarray · optionalThe partner's contacts. If none is marked primary, the first becomes primary.
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