Skip to content
BuildBase
HTTP API menu

Get a proof-of-work challenge for the hosted sign-up page

Returns a fresh, single-use challenge bound to sign-up when the org's sign-up captcha is the built-in one, and 404 when sign-up does not use a challenge.

GET/api/v1/auth/captcha/challenge

Sign-in
No credential. Name the organization with the hosted sign-in state header or the org query parameter.
Rate limit
Up to 500 requests every 3 seconds per IP address; up to 1,000 requests a minute per API key (some requests are not counted); up to 30 requests a minute per IP address.

Returns a fresh, single-use challenge bound to sign-up when the org's sign-up captcha is the built-in one, and 404 when sign-up does not use a challenge. Sent with Cache-Control: no-store.

Request

This operation takes no parameters and no body.

Example request

Replace each YOUR_... value with your own.

curl -X GET "https://api.console.buildbase.app/api/v1/auth/captcha/challenge?org=YOUR_ORG_ID"
const response = await fetch(
  'https://api.console.buildbase.app/api/v1/auth/captcha/challenge?org=YOUR_ORG_ID',
  {
    method: 'GET',
  }
);
if (!response.ok) {
  throw new Error(`${response.status}: ${await response.text()}`);
}
const data = await response.json();
import requests

response = requests.get(
    "https://api.console.buildbase.app/api/v1/auth/captcha/challenge?org=YOUR_ORG_ID",
    timeout=30,
)
response.raise_for_status()
data = response.json()

Responses

200 OK

OK

Example
{
  "algorithm": "SHA-256",
  "challenge": "f181784692944189266f9a87fdd221a55eaac30dbb45f0a7227bc8eccd37dd94",
  "maxnumber": 100000,
  "salt": "000000000000000000000001?s=eb87e9420b8001e60ad7926a4df42109&expires=1794382733",
  "signature": "[REDACTED]"
}

Any other status

Any other answer the handler sends itself (its own refusals). Not described yet.

Errors

Each refusal, what it means, and what to do. The request changed nothing.

401 Unauthorized

What it means: The credential is missing, expired or not accepted here, or the caller's role has no grant for x-permission (refused with 401 too). The body is the plain text Unauthorized, or a JSON body with a code where the gate says why.

What to do: Send the credential this operation asks for (see Sign-in above), or sign in again if it expired. A valid credential is also refused when the role has no grant for the permission above.

Example
Unauthorized

429 Too Many Requests

What it means: A rate limit in x-rateLimit was reached. retryAfter and the Retry-After header say how many seconds until the window resets.

What to do: Wait the number of seconds in the Retry-After header (also retryAfter in the body), then retry. Slow down repeated calls.

Example
{
  "success": false,
  "message": "string",
  "reason": "rate_limited",
  "retryAfter": 1
}