API access
HTF supports personal API keys and service-account keys for customer integrations. The current customer API key surface is read only. Use a station's own API key for station operations; it is a different credential with a different access boundary.
Personal keys
Open My Account → Personal API Keys to create a key. Choose an organisation, the projects it may access, the permissions it needs, and an expiry. A personal key remains limited by its owner's current organisation membership and project grants. Save the value when it is shown; it will not be displayed again.
Service accounts
Organisation administrators can manage service accounts in Identity → Service Accounts. Use one for an unattended integration rather than a person's key. Restrict its project scope and permissions, and revoke the token when the integration is retired.
Available permissions
| Permission | Access |
|---|---|
projects:read | Discover selected projects. |
stations:read | Read station identity and status. |
runs:read | Search runs and inspect stage results. |
logs:read | Read paginated run logs; also requires runs:read. |
Grant only the permissions the integration needs. A key with one permission does not automatically receive another. The HTF application links to the customer API reference at /docs/api/ on your deployment; use that reference for the supported endpoints and request formats.