SaaS products Ledgerly API clients
API clients · Ledgerly
External systems calling into this app. Keys are shown once; for outbound calls see API connections.
| Client | Scopes | Status | |
|---|---|---|---|
| Production server bwk_live_••••a1c9 | read:tenants write:records | Active | |
| Reporting job bwk_live_••••a1c9 | read:records | Active | |
| Legacy sync bwk_live_••••0000 | read:tenants | Revoked |
About this page
Keys that let other systems call into your product — the inbound direction. Each key is scoped and revocable, and the secret is shown exactly once at creation; after that even we can’t display it, only replace it.
Behind this page/apps/:saasAppId/api-clients · CanManageApiKeys
Retrieve
sp_Builder_ListApiClients returns clients, scopes, and status — never the secret or its hash.Save
Create →sp_Builder_CreateApiClient (app generates secret, stores hash, shows raw once); RotateApiSecret; RevokeApiClient.Success
- Raw secret is displayed once and never returned again.
- Keys are scoped, rate-limited, auditable, and revocable.
- The gateway applies the same server-side field permissions and data masking used by the visual runtime.
- External apps never receive unrestricted database access.
CLI handoff
Implement this scaffold from the structured contract, then remove hard-coded preview rows. The source of truth is CLI Handoff and admin-cli-manifest.json.
Page IDapp-api-clients
Route/apps/:saasAppId/api-clients
AccessCanManageApiKeys
Statusjourney-aligned-scaffold
Server-inject identity and scope values; never trust browser-supplied account, app, tenant, user, entitlement, price, or permission identifiers. Preserve the loading, empty, forbidden, failed, retrying, and completed states shown by the preview.