KERNIT Documentation
Team Admin API
Team API surfaces let institutions and product teams manage organization keys, shared presets, usage, members, billing, and top-ups around KERNIT document-processing workflows.
Organization Surfaces#
| Endpoint | Purpose |
|---|---|
| GET /org | Load organization account state. |
| GET/POST/DELETE /org-keys | Manage organization API keys. |
| GET/POST /org-presets | Manage shared hyperlink settings presets. |
| GET /org-usage | Inspect team usage history. |
| POST /org-billing | Create or complete organization billing actions. |
| GET/POST /org-members | Manage team membership when enabled. |
Schema-backed Key and Team Operations#
| Method | Endpoint | Summary |
|---|---|---|
| GET | /api-keys | List individual API keys |
| POST | /api-keys | Create an individual API key |
| DELETE | /api-keys | Revoke an individual API key |
| GET | /org-keys | List organization API keys |
| POST | /org-keys | Create organization API key |
| DELETE | /org-keys | Revoke organization API key |
| GET | /org-presets | List shared organization presets |
| POST | /org-presets | Create shared organization preset |
| GET | /org-usage | List organization usage |
Operational Guidance#
Use separate keys for production, staging, and one-off testing. Keep shared presets stable so scan and apply requests use the same settings. Review organization usage regularly when processing large document batches.
Was this page useful?Send a lightweight docs feedback event.