InfiniteRanks documentation
Authenticate with a scoped read-only workspace key
A developer key grants read-only access to one workspace’s saved records. Treat it as a credential even though it cannot start paid collection.
Create and store the key
Create a key from the intended workspace’s developer controls using an authorized account. Give it a meaningful client name and choose the appropriate expiry. Copy the secret into a trusted server secret store or compatible client configuration. The metadata view retains the prefix and lifecycle information, not a reusable display of the secret.
Send a Bearer header
Use Authorization: Bearer <your-key> over HTTPS. For example, request GET https://app.infiniteranks.com/api/v1/workspace with that header. Do not send the key in a URL query string, public source file or browser bundle. Developer endpoints do not accept cookie authentication as a substitute for the required key.
Handle rejection and throttling
An invalid, expired or revoked key cannot read workspace records. Browser requests are subject to origin checks; there is no permissive cross-origin developer access. The rate allowance is workspace-scoped rather than a way to multiply throughput by creating keys. On 429, honor Retry-After and avoid immediate repeated retries.
Rotate deliberately
The implementation permits up to ten active keys per workspace and supports explicit revocation. Remove unused client keys and revoke exposed ones. Test a new key with the workspace context route before replacing an active integration. Keep each client’s credentials distinguishable so the owner can review access and revoke the correct connection.
Sources and further reading
Sources explain the underlying standards. They do not endorse InfiniteRanks or guarantee a ranking outcome.