Sign in

Generate challenge

POST https://{organization}.myguper.com/api/connect/pow/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)

Modes

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

Name Type Description
x-guper-authorization * string User token issued by Guper.
Content-Type * string Always `application/json` for endpoints that accept a JSON body.

Request body

Content-Type: application/json

{
    "login": "maria.silva"
}

Responses

{
    "challenge": "a1b2c3d4e5f6...64 hex characters",
    "target": "0000ffffffffffff...64 hex characters"
}
Copied to clipboard