CryptoHub enforces dual login: a single administrator is not fully authenticated until a second administrator has also logged in within the same session. The two logins share one cookie jar, and the bearer token is only minted once the session is fully logged in.Documentation Index
Fetch the complete documentation index at: https://docs.futurex.com/llms.txt
Use this file to discover all available pages before exploring further.
Log in with dual login
Log in as The first login responds with
Admin1, then Admin2, writing to a shared cookie jar (-c writes, -b reads):Dual login
fullyLoggedIn: false; after the second login the session is complete:Second login response (truncated)
A subsequent read-only call such as
GET /api/v2/x509/cert-profiles/stubs should return HTTP 200 with "success": true. If you receive HTTP 401 or "errorCode": "InvalidAuthToken", the token has expired; repeat this step to mint a fresh one.
