Version: 1.0

Hackihub Client API

Hackihub API surface available to tenant admins and users (client-api endpoints only)

Authentication

OAuth 2.0: oauth2

Authentik OAuth2 Authorization Code flow (PKCE).

After completing the flow the resulting JWT access token is sent in the Authorization header:

Authorization: Bearer <jwt>

All endpoints accept this auth method.

Security Scheme Type:	oauth2
OAuth Flow (authorizationCode):	Token URL: https://auth.kvantumci.com/application/o/token/ Authorization URL: https://auth.kvantumci.com/application/o/authorize/ Scopes: email: Access to your email profile: Access to your profile openid: OpenID Connect

HTTP: Bearer Auth

Personal Access Token (PAT) or Global Access Token (GAT).

Send the token in the Authorization header (same header as OAuth2 JWT):

Authorization: Bearer <token>

Token values carry a mandatory prefix: pat_… for personal tokens, gat_… for tenant-wide tokens — this prefix is how the server distinguishes them from OAuth2 JWTs.

Only endpoints tagged client-api accept this auth method.

Security Scheme Type:	http
HTTP Authorization Scheme:	bearer
Bearer format:	PAT/GAT

API Key: api-key

Shared API key for machine-to-machine endpoints. Send Api-Key (canonical); x-api-key is also accepted.

Security Scheme Type:	apiKey
Header parameter name:	Api-Key