We have made some upgrades to API keys: the keys that connect your backend, CI and scripts to Trigger.dev to trigger tasks, read runs and deploy.
Here's what's new:
- Set access per permission area (a group of API endpoints, like runs)
- Combine presets (named permission bundles) in one key
- Save your own presets for your organization
- See and edit each key's access
- Limit keys by IP
All of this is available on every Trigger.dev Cloud plan, including Free and Hobby.
Custom access
If no single preset fits, set a level for each of 15 areas, like Runs, Deployments and Webhooks. The levels depend on the area, from None and Read up to Read and write or Manage. The custom access docs list them all.
Saved presets
Save custom access as a preset for your organization (up to 50). It appears in every project and environment, so your team creates each kind of key the same way.
See and edit a key's access
Each key now shows when it last used each area.
Click Edit access to change what any active key can do, except the root key (each environment's default full-access key), and see what it gains and loses before saving.
Narrow to what it used
Once a key has at least 7 days of usage, you can click Narrow to what it used to trim the access to what it needed in the past 30 days, or since it was created if the key is newer than that. You review the change before saving, and it applies without a redeploy.
IP allowlists
Limit a key to up to 50 IP addresses or CIDR ranges, like your CI runners or servers.
Changes to expiry
New keys expire after 90 days by default, or you can pick 30 days, 1 year or a custom date. Existing keys don't change.
Learn more
Create a key on the dashboard's API keys page. The API keys docs and custom access docs cover every preset and area.