Authentication
Personal API keys, workspace access, and required scope.
Create an API key
Send your if_pat_ personal API key in the Authorization header on every request:
Authorization: Bearer if_pat_...
All three methods require incidents:read. The key is tied to one workspace and to the user who created it. The user must remain active and a current member of that workspace. Revoked or expired keys, inactive users, and removed memberships return 401. A valid key without incidents:read returns 403. Workspace keys (if_wst_) are not accepted by these methods.
The application also continues to use its existing JWT access tokens for these methods. Do not put a token in a URL, query string, or example shared with others.