Generate challenge
Generates a Proof of Work challenge that must be solved before authenticating. The client computes SHA-256(challenge + nonce) until the hash is lexicographically less than or equal to the returned target. The solved nonce is then sent alongside the login credentials to the Auth endpoint.
Each new challenge for the same login invalidates the previous one, preventing parallel brute-force attacks. Difficulty escalates exponentially based on the number of challenge requests within a sliding 15-minute window.
Try-it values populated from environment ACME (Demo)
Called by internal services (Admin panel, other microservices) using RSA signature authentication.
Authentication
Token
Most Connect endpoints require a valid x-guper-authorization token.
Token issuance itself (/api/connect/auth) is the exception — it
uses the x-guper-apikey and x-guper-apisecret credentials.
Headers
Request body
Content-Type:
application/json