Authentication
All calls to the Felt API authenticate with a personal access token sent as a Bearer token in the request header:
Authorization: Bearer <API Token>Tokens start with the felt_pat_ prefix. Since a token grants access to your account, store it securely — treat it like a password. Prefer environment variables or a secrets manager over hardcoding tokens in source code.
Creating a token
You can create an API token in the Developers tab of the Workspace Settings page:



Be sure to take note of the token before closing the dialog; you won't have a second chance to view it. Only a hash of your token is stored on Felt's servers.
How tokens behave
Workspace-scoped. Each token belongs to the workspace it was created in and can only access that workspace's resources. Requests against another workspace's resources fail with
401.They act as you. Requests made with your token have your account's permissions in that workspace.
No expiry. Tokens remain valid until revoked. To rotate a token, create a new one in workspace settings, switch your integration over, and revoke the old one.
Failed authentication returns
401with a JSON body explaining the problem — see Errors and rate limits.
Making an authenticated request
A successful response returns your user details, confirming the token works:
From here, head to Getting started to create your first map via the API.
Last updated
Was this helpful?