Skip to main content
The RoScripts API is open by default — you can call every endpoint anonymously, rate-limited by IP. An API key is optional and does one thing: it raises your limits.

Anonymous

No key. Limited by IP. max page size capped at 20. Perfect for trying things out and light traffic.

With a key

Higher per-minute and per-day limits. max page size up to 100. Best for hubs and production traffic.

​
Getting a key

1

Sign in to RoScripts

Head to your account settings on roscripts.io. You’ll need a verified email.
2

Create an API key

Open the API keys section and click Create key. Give it a name you’ll recognise (e.g. “my-hub-prod”).
3

Copy it once

The full key is shown exactly once, at creation. Store it somewhere safe — we only keep a hash, so we can’t show it again.

​
Using a key

Send it as a Bearer token in the Authorization header:
Treat your key like a password. Don’t ship it in client-side JavaScript or commit it to a public repo. If a key leaks, revoke it from your account settings and create a new one — revocation takes effect within seconds.

​
How keys are stored

We store only a SHA-256 hash of your key, never the raw value — the same way password-reset tokens are handled across Sirius. A database leak can’t be turned into working keys. The trade-off: we genuinely cannot recover a lost key, so keep it safe and rotate if in doubt.

​
Tiers

See Rate limits for the exact request budgets per tier.
An invalid or revoked key never hard-fails your request — the API simply treats you as anonymous and applies anonymous limits. So a rotated key degrades gracefully instead of returning 401.