Authentication
Login
Exchange your email and password for a JWT access token and refresh token.
The
access token expires after 1 hour. The refresh token expires after 30 days.Tokens
Token Refresh
Use the refresh token to obtain a new access token without re-authenticating.
If the refresh token has expired, you must log in again to get a new pair of tokens. Refresh tokens are rotated on each use — the old refresh token is invalidated when a new one is issued.
Usage
Using the Access Token
Include the access token in the
Authorization header of every API request:API Keys
API Key Authentication
For server-to-server integrations where storing user credentials is not ideal, ParsaLink supports workspace-level API keys.
Creating an API Key
- Go to Settings → API Keys.
- Click Create API Key.
- Give the key a name (e.g., “Zapier Integration” or “Internal Dashboard”).
- Copy the key — it is only shown once.
Usage
Using an API Key
API keys use the same
Authorization: Bearer header format:API keys are scoped to the workspace, not to an individual user. Actions performed with an API key are attributed to a system user in activity logs.
Management
Revoking an API Key
Go to Settings → API Keys, find the key, and click Revoke. The key stops working immediately.Example
Example: Full Authentication Flow
Example flow showing login, authenticated request, and token refresh.
Security
Security Best Practices
Follow these best practices to keep your API usage secure.
- Never hardcode credentials — Use environment variables for tokens and API keys.
- Store refresh tokens securely — Treat them like passwords.
- Rotate API keys regularly — Create a new key and revoke the old one periodically.
- Use HTTPS only — All API communication must be over TLS. HTTP is not supported.
- Monitor key usage — Review API key activity logs in Settings → API Keys to detect unauthorized access.
