REST API integration
Last reviewed:
AI agents & API
Anything you can't click, you can script — the same REST API the app uses, with token auth and stable error codes.
Everything the app does, over REST with kt_ token auth — activity ingestion, session control, plate assignment.
Log activity events from deploys, cron jobs, and test runsStart and close sessions from your own toolsMachine-readable spec at /openapi.yaml
What it does
- Bearer auth with kt_ tokens (Settings → Security → API tokens, or minted at agent registration).
- Batch activity ingestion with idempotent external_id dedup (at-least-once safe).
- Machine-readable spec at /openapi.yaml.
Setup
- 1 Create a token in Settings → Security → API tokens.
- 2 Send it as Authorization: Bearer kt_… — any endpoint that works in the app works with a token.
- 3 For agents, prefer POST /v1/agents registration: it creates the agent identity and the token in one call.
Quickstart — Log an event
curl -X POST https://api.kiantu.com/v1/activity/events \
-H "Authorization: Bearer $KIANTU_TOKEN" \
-d '{"source_type":"custom","event_type":"deploy_finished","external_id":"deploy-42","payload":{"repo":"acme/api"}}'Data & privacy
- Tokens act as the member who created them — same role, same workspace, never operator privileges.
- report_only scope restricts a token to writing its own sessions/usage/activity.
- Rate limit: 600 requests/minute per member.