The API in five minutes
Everything an operator can do in the studio can be done over the API. A key acts on behalf of the workspace.
- 1Create a keySettings, API access. Choose the role, and whether the key may only read. A writing administrator key can delete a portal.
- 2Send it alongThe Authorization header on every call. The key is shown once only, when it is created.
- 3Ask what existsFetch capabilities and vocabulary before you hard code anything. Those two tell you what this installation can do.
curl https://api.kilango.com/v1/capabilities \
-H "Authorization: Bearer hub_live_…"Keys are replaced without downtime
Replacing a key creates a new one and lets the previous one keep working for another day. The two appear as a single pair in the list, the previous one indented under its successor with "closes tomorrow at 2.20 pm" and Close now.
Once a key is gone it cannot be shown again. The way out is always replacement, never showing it a second time.