Authentication¶
All API requests require an API token passed as a Bearer token in the Authorization header.
Getting a token¶
- Sign in at app.instatollm.com
- Navigate to API Tokens in the sidebar
- Click Create token, enter a descriptive name, click Create
- Copy the token immediately — it is shown only once
Tokens look like:
The ist_ prefix identifies it as an instatollm token.
Using the token¶
Include the token in every request:
Managing tokens¶
List tokens¶
Tokens are visible at app.instatollm.com/api-tokens. Each token shows its name, creation date, and last used time.
The actual token value is never shown again after creation —
only the first 16 characters (ist_xxxx…) are displayed for identification.
Revoke a token¶
Click Revoke next to any token in the dashboard. Revocation is immediate — any in-flight requests with that token will fail.
Security best practices¶
- Give each integration its own token (one for n8n, one for Zapier, etc.)
- Revoke tokens that are no longer needed
- Never commit tokens to git — use environment variables
- Tokens do not expire, but you can rotate them at any time
Error responses¶
| Status | Meaning |
|---|---|
401 Unauthorized |
Missing Authorization header |
401 Unauthorized |
Invalid or revoked token |
403 Forbidden |
Token valid but insufficient permissions |