Access Token
What Is an Access Token?
An access token is a software credential that lets an application call a protected API with specific permissions. It represents authorization, not identity, and should be treated as a secret. Tokens commonly include scopes, an intended API audience, and an expiry time.
How an Access Token Works
- A user or service approves requested permissions.
- An authorization server issues a token.
- The app sends it in an Authorization: Bearer header.
- The API validates it and permits only allowed actions, such as reading a calendar but not deleting events.
Access Token vs. ID Token vs. Refresh Token
| Token | Purpose | Handling |
|---|---|---|
| Access | Call an API | Send only to its intended API |
| ID | Describe a signed-in user | Use in the client, not for API access |
| Refresh | Obtain new access tokens | Store with stricter protection |
A JWT is a possible token format, not a synonym for an access token.
Benefits of Access Tokens
They support safer integrations.
- Scopes enforce least-privilege access.
- Short expiry limits exposure.
- Apps can access APIs without receiving a password.
Practical Limits and Security Risks
Tokens can still be misused if stolen.
- Broad scopes and leaked logs can expose data.
- Expired tokens cause failed requests.
- Revoking self-contained tokens may be difficult.
Access Token Security Checklist
- Use HTTPS, short expiry, minimal scopes, and server-side storage where possible.
- Never place tokens in URLs, source control, or logs.
- Validate signature, issuer, audience, expiry, and scopes at the API.
- Treat personal access tokens, including GitHub personal access tokens, like passwords.
Access Tokens in Apps Built With Emergent
When building API integrations with Emergent, use secure token handling and least-privilege permissions. Explore the Token glossary, Learn hub, and AI tools for software development resources for practical guidance.
on Emergent today

