Activate a partner

POST/lokta-lms/api/v1/sourcing-partners/{partnerId}/activation

Activates a sourcing partner, so loans can be attributed to it.

Moves pending or inactive → active. Until this happens the partner cannot be attributed a loan, which is what makes this the step that closes onboarding rather than a cosmetic flag.

Refused with 422 sourcing/partner_has_no_active_terms unless an agreement is in force. An active partner can be attributed loans, and activating one with no terms would leave the lender owing fees on no agreed basis; a gap that otherwise surfaces at the first fee run rather than while somebody could still fix it.

reason is optional here: activation is the expected end of onboarding and explains itself. It is recorded in status_history either way.

onboarded_on is stamped the first time a partner becomes active and never overwritten; a partner reactivated in 2028 was still onboarded when it first went live.

When to use it

This is the last step of onboarding. Call it once terms are in place.

Worth knowing

Refused with 422 sourcing/partner_has_no_active_terms when no agreement is in force.

Path parameters

partnerIdpath · string · required

Opaque partner id, spr_…

Header parameters

Idempotency-Keyheader · string · optional

Per-intent key

Request body application/json

reasonstring · optional

Optional here. Activation is the expected end of onboarding.

Responses

defaultdefault response

Every 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

curl -X POST \ 'https://default.lokta.tech/lokta-lms/api/v1/sourcing-partners/{partnerId}/activation' \ -u '{username}:{password}' \ -H 'Tenant-Identifier: default' \ -H 'Content-Type: application/json' \ -d '{ "reason": "string" }'

import requests response = requests.post( "https://default.lokta.tech/lokta-lms/api/v1/sourcing-partners/{partnerId}/activation", auth=("{username}", "{password}"), headers={"Tenant-Identifier": "default"}, json={ "reason": "string" }, ) print(response.json())

const response = await fetch("https://default.lokta.tech/lokta-lms/api/v1/sourcing-partners/{partnerId}/activation", { method: "POST", headers: { Authorization: "Basic " + Buffer.from("{username}:{password}").toString("base64"), "Tenant-Identifier": "default", "Content-Type": "application/json", }, body: JSON.stringify({ "reason": "string" }), }); console.log(await response.json());

HttpClient client = HttpClient.newHttpClient(); HttpRequest request = HttpRequest.newBuilder() .uri(URI.create("https://default.lokta.tech/lokta-lms/api/v1/sourcing-partners/{partnerId}/activation")) .header("Authorization", "Basic " + Base64.getEncoder().encodeToString("{username}:{password}".getBytes())) .header("Tenant-Identifier", "default") .header("Content-Type", "application/json") .method("POST", HttpRequest.BodyPublishers.ofString(""" { "reason": "string" } """)) .build(); HttpResponse<String> response = client.send(request, HttpResponse.BodyHandlers.ofString()); System.out.println(response.body());

payload := strings.NewReader(`{ "reason": "string" }`) req, _ := http.NewRequest("POST", "https://default.lokta.tech/lokta-lms/api/v1/sourcing-partners/{partnerId}/activation", payload) req.SetBasicAuth("{username}", "{password}") req.Header.Set("Tenant-Identifier", "default") req.Header.Set("Content-Type", "application/json") res, _ := http.DefaultClient.Do(req) defer res.Body.Close() data, _ := io.ReadAll(res.Body) fmt.Println(string(data))