Overview
API tokens provide secure authentication for programmatic access to your Graphor projects and flows. They are essential for:- Connecting applications to your RAG pipelines via REST API
- Integrating with AI assistants through MCP Server
- Automating processes with Graphor resources
- Building custom integrations with your existing tools
Creating API Tokens
To create a new API token:- Navigate to your project in Graphor
- Click on API Tokens in the left sidebar
- Click the Create New Token button
- Enter a descriptive name for your token (e.g., “Production REST API” or “Claude Integration”)
- Click Create
- Important: Copy your token immediately and store it securely. For security reasons, the full token will only be displayed once.
Managing Tokens
The API Tokens page provides several management capabilities:Revoking Tokens
To revoke a token that is no longer needed or may be compromised:- Navigate to the API Tokens page
- Find the token you want to revoke
- Click the Delete icon next to the token
- Confirm the revocation
Using API Tokens
API tokens are used in different ways depending on your integration method:REST API
For REST API integrations, include your token as a Bearer token in the Authorization header:MCP Server
For MCP Server integrations, include your token in the environment configuration:Token Security Best Practices
API tokens provide access to your Graphor resources, so it’s important to handle them securely:Storage
- Never store tokens in public repositories or client-side code
- Use environment variables or secure secret management systems
- For development environments, consider using .env files (excluded from version control)
Distribution
- Share tokens securely with team members who need access
- Use encrypted channels for token distribution
Rotation
- Regularly rotate tokens used in production systems
- Immediately revoke tokens when team members leave or roles change
- Create new tokens rather than sharing existing ones for new integrations
Troubleshooting Token Issues
Authentication failures
Authentication failures
Solutions:
- Verify you’re using the full token string
- Check that the token hasn’t been revoked
- Confirm you’re using the correct Authorization format
Access denied errors
Access denied errors
Solutions:
- Verify the token is assigned to the correct project
- Ensure the resources you’re accessing exist
- Create a new token with appropriate permissions if needed
Security concerns
Security concerns
Solutions:
- Immediately revoke any potentially compromised tokens
- Create new tokens with fresh credentials
- Update security practices for token storage

