Skip to main content
API keys let external applications talk to Technified. Your Roblox games use them to check ban status and sync moderation, and custom tools can use them to read server data. Open Settings > API Keys in the sidebar.

​
What a key shows

The full key is shown only once, at creation. Copy it immediately and store it somewhere safe.

​
Create a key

1

Create

Click Create API Key.
2

Name it

Add an optional name, for example “Main Game” or “Test Server”.
3

Choose scopes

Tick the scopes the key needs. A key with no scopes authenticates but cannot call any endpoint, so grant at least one.
4

Set controls (optional)

Optionally add an expiry date, a per-key rate limit, or an IP allowlist.
5

Copy it now

Copy the key right away. It will not be shown again.
You can have up to 10 API keys per server. Revoke an unused key to free a slot. See Limits for all creation limits.

​
Scopes and controls

Each key is scoped: it can only call the endpoints whose scopes you granted. Grant the least a key needs. A :write scope implies the matching :read scope for the same resource. You can change a key’s scopes and controls later with Edit, without regenerating it. Beyond scopes, each key can carry optional guards:
  • Expiry: a date after which the key is rejected.
  • Rate limit: a per-key requests-per-minute cap, on top of the global rate limits.
  • IP allowlist: restrict the key to specific IPs or IPv4 CIDR ranges.
Keys created before scoping keep full access. Editing such a key applies the scopes you pick. Keys installed by the Roblox integration quick-install request every scope automatically, so the plugin keeps working.

​
Use a key

Store the key in a server side script only, never in client scripts:
The Technified module and the Roblox integration read this key automatically.

​
Manage keys

​
Security

  • Never share keys publicly or commit them to version control.
  • Name keys by purpose so you know which is which.
  • Rotate keys periodically: create a new one, update your apps, then revoke the old one.
  • Watch the Last Used date and revoke anything that looks wrong.

​
Troubleshooting

Check the key is copied in full and has not been revoked. Make sure it is for the correct server.
The key does not have the scope that endpoint needs (a 403 with insufficient_scope). Open the key, click Edit, and add the scope shown in the error.
The key passed its expiry date. Create a new key (or edit the old one’s expiry) and update your app.
You are sending too many requests. Wait, then try again, and consider caching responses. A per-key rate limit may also be set on the key itself.