Lokta Lending Platform API

The staff lending console's core, as a curated REST reference — … endpoints across … sections, grouped by what they do. Every request authenticates with HTTP Basic and names its tenant; every write follows the platform's date and command conventions.

Start here

API Reference Every endpoint with parameters, schemas, and copy-runnable samples in five languages. ⌘K searches all of it. Conventions Auth, the tenant header, dates & locale, commands, pagination, errors, idempotency — read once, applies everywhere. OpenAPI spec The curated document this site renders — feed it to Postman or a code generator. The raw build spec stays at /openapi.json.

Your first call

Point at the core

Every path in the reference hangs off the API base URL. This instance:

…

Authenticate and name the tenant

HTTP Basic credentials of an application user, plus the Tenant-Identifier header on every request.

List loan accounts

…

From here, the Reference has the other endpoints — and the Conventions page explains the date format you will meet on your first write.

Generated from the running build's OpenAPI document by api-docs/scripts/enrich.mjs — the curation (hidden sections, renames, grouping) is baked into openapi.curated.json, not filtered in the browser.