Credential security
Rotate, revoke, and change the permissions of workspace API keys.
- PlanFree for read-only keys, Pro for write access
- WhoOwners, admins, and members
Rotate and revoke keys
Rotate a key
In the key's row menu, choose Rotate secret. Project Feed creates a new secret with the same creator, name, and expiration and revokes the old secret at once. Update your secret manager before you close the dialog.
Revoke a key
Choose Revoke when a secret may have leaked. Requests that use it return 401 right away. A revoked key cannot be restored, so create a new one.
List and revoke keys with the API
GET /api/v1/api-keys lists the workspace's active keys and needs workspace:read. Owners and admins see every key, and other members see only their own. Each key has its name, keyPrefix, scopes, creation, last use, and expiry times, and its creator. The secret is never returned. Send limit from 1 to 100, and pass nextCursor as cursor while hasMore is true.
DELETE /api/v1/api-keys/:keyId needs workspace:write and revokes the key at once. Owners and admins can revoke any key. Other members can revoke only keys they created, and get 403 for the rest. An unknown key returns 404 and a key that is already revoked returns 409. Creating, rotating, and editing keys stay in the app.
curl https://projectfeed.app/api/v1/api-keys \
-H "Authorization: Bearer pf_YOUR_API_KEY"
curl --request DELETE https://projectfeed.app/api/v1/api-keys/key_abc123 \
-H "Authorization: Bearer pf_YOUR_API_KEY"Rotation has no overlap. To switch a running job without downtime, create a second key, move the job to it, then revoke the first.
Change permissions and audit use
- Choose Edit permissions in a key's row menu to change its scopes. The change applies to the next request and the secret stays the same.
- The Allowed API scopes policy caps what new and rotated keys can request. Existing keys keep their scopes until you edit or revoke them.
- Creating, rotating, and revoking keys appear in the audit log. The key list shows when each key was last used.
Fix ownership problems
- The key's creator left
- The key stops working. Rotation keeps the original creator and does not help. Create a replacement key under an active member, update the automation, and revoke the old key.
- Rotation would interrupt production
- Create a second key with the same permissions, deploy it, check traffic, and then revoke the first.
To remove a creator without breaking automations, create the replacement keys under another active member first.