Attribute a loan to a partner
/lokta-lms/api/v1/loan-attributionsAttributes a loan to the active partner that sourced it.
One partner per loan, and this is enforced: a second attribution is a 409 sourcing/loan_already_attributed, not a second row. Correct the existing one instead.
Only an active partner may be attributed: a pending partner has not finished onboarding and an inactive one has been stood down, and attributing to either creates a fee liability to a party the lender has not agreed to pay.
source defaults to at_origination. backfill must be stated deliberately, because a backfilled attribution is an assertion about a past nobody witnessed.
For a Direct loan, do not call this at all.
When to use it
Use this to record which partner sourced a loan. The partner has to be active. For a Direct loan, do not call it.
Worth knowing
- A loan has one partner. A second attribution returns 409, so correct the existing one instead.
- Send an Idempotency-Key header.
Header parameters
Idempotency-Keyheader · string · optionalPer-intent key; persist it before sending and reuse it on retry
Request body application/json
loan_idinteger · optionalPlaceholder name, to be confirmed. The loan to attribute.
partner_idstring · optionalPlaceholder name, to be confirmed. The active partner the loan is attributed to.
sourcestring · optionalWhere the attribution came from. Defaults to at_origination; a backfill has to be stated deliberately.
at_origination, backfillResponses
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