Your personal API token lets external tools and scripts authenticate to the Alta API on your behalf — for example, to trigger a call or push prospects into a campaign.
Who this is for: Anyone wiring up a custom integration, automation, or script against the Alta API. No developer role is required — every user can generate their own token.
Before you start
You'll need access to your own Settings in Alta. The token is personal to your user — actions made with it run as you, using your access.
You can have one active API token at a time. Generating a new one (or regenerating) replaces any previous token.
Have somewhere safe to store the token, such as a password manager or your tool's secrets store.
Generate a token
Open your user settings and go to Settings → API tokens (direct path:
/user/settings/api-tokens). You'll see the API tokens page with an API token card.If you don't have a token yet, click Generate token.
A success message confirms "API token created successfully." Your token now appears in the field on the card.
The token is masked for security. Click the copy button next to it to copy the full value to your clipboard.
Paste the token into your integration, script, or secrets store right away.
Use the token in an API request
Send the token as a Bearer token in the Authorization header on every request to the Alta API:
Authorization: Bearer YOUR_API_TOKEN
If your user belongs to more than one account, also include an account header so Alta knows which account to act in:
x-account-id: YOUR_ACCOUNT_ID
Regenerate a token
On the API token card, click Regenerate token.
A confirmation dialog titled "Are you Sure?" explains: regenerating will invalidate your current token and you'll need to update any existing integrations that use it. This action cannot be undone.
Click Regenerate Token to confirm, or Cancel to keep your current token.
On success you'll see "API token regenerated successfully," and a fresh token replaces the old one. Copy and update your integrations.
Tips and common pitfalls
You only see the full token in the field. Always copy it with the copy button and store it securely — treat it like a password.
Regenerating breaks live integrations. The old token stops working immediately, so any tool still using it will start getting
401 Invalid API tokenerrors until you paste in the new one.The token acts as you. Requests run with your user's access and permissions. If your access to something is removed, requests using your token lose that access too.
Multiple accounts? If you don't send the
x-account-idheader, the API returns an error telling you to provide the account header. Send the ID of the account you want to operate in.One token per user. There's no list of multiple named tokens — generating or regenerating always produces a single current token.
Related
How to Trigger a Call via API
How to Add Prospects via Webhook URL
]]>