Personal access tokens let scripts and integrations authenticate as you when calling the Elevated Signals API outside the browser — for example, to pull data into a spreadsheet, a BI tool, or a custom integration. You can create and revoke your own tokens from your profile, without contacting support.
A few things to know before you create one:
A token acts as you. It has the same access your account does — nothing more, nothing less.
It grants full API access to your account and does not expire. Treat it exactly like a password.
It is shown only once. Copy it as soon as it is generated and store it somewhere secure. If you lose it, you cannot view it again — you will need to create a new one.
Revoke it the moment it is no longer needed, or if you suspect it has been exposed.
Creating a token
Open the profile menu by clicking your name in the bottom-left corner of the app, then select Edit Profile.
On your profile page, click Manage API tokens in the top-right.
Click Generate your first token (or Generate new token if you already have one).
In the panel that opens, re-enter your account password to confirm, then click Generate New Token.
Copy your token right away and store it securely — in a password manager or your platform's secrets manager. For security, it is displayed only once and cannot be retrieved later.
Shortcut: once signed in, you can go straight to your tokens at https://<your-subdomain>.elevatedsignals.com/dashboard/profile/api-tokens (most customers log in at dashboard.elevatedsignals.com).
Using your token
Use your token to authenticate requests to the Elevated Signals API. For the exact request format, authentication header, and the full list of available endpoints, open the profile menu and select API Documentation.
Revoking a token
If a token is no longer needed — or you think it may have been exposed — revoke it:
Go to Edit Profile → Manage API tokens.
Find the token in your list and revoke it.
Revoking takes effect immediately: any script or integration still using that token will stop working, so make sure to update those systems with a new token first.
Best practices
Use a separate token per integration. If one is ever compromised, you can revoke just that one without breaking everything else.
Never share a token or commit it to source code. Keep it in a password manager or secrets manager.
Revoke tokens you no longer use. Fewer live credentials means less risk.
Rotate immediately if exposed — revoke the old token and generate a new one.