API tokens provide secure, programmatic access to Meetzy’s platform without requiring user credentials. These tokens act as secret keys that authenticate your applications and services.
Never share API tokens or expose them in client-side code. Treat them like passwords and store them securely in your server environment.
Accessing Token Manager
Navigate to your account settings to manage API tokens:
Open Account Menu
Click on your profile avatar in the top-right corner of the dashboard
Select Account Settings
Choose “Account Settings” from the dropdown menu
Access Token Manager
Click on the “API Tokens” tab to view your token management interface
Creating a New Token
Click New Token
Click the “New Token” button in the token manager interface
Enter Token Details
Provide a descriptive name for your token (e.g., “Production API”, “Analytics Service”)
Set Expiration Period
Choose an expiration timeframe:
- 30 days - Short-term testing
- 90 days - Medium-term projects
- 6 months - Long-term integrations
- 1 year - Annual renewals
- No expiration (4 years) - Permanent access
Generate Token
Click “Create Token” to generate your new API token
Copy Token Securely
Important: Copy the token immediately. For security reasons, the full token value will never be displayed again
Choose expiration periods based on your security requirements. Shorter expiration periods are more secure but require more frequent renewal.
Token Security Best Practices
Storage Guidelines
- Store tokens in environment variables, not in code
- Use secure secret management services in production
- Never commit tokens to version control systems
- Rotate tokens regularly based on your security policy
Access Control
- Create separate tokens for different applications or environments
- Use descriptive names to easily identify token purposes
- Revoke unused or compromised tokens immediately
- Monitor token usage through API logs
Environment Separation
# Development environment
MEETZY_API_TOKEN=your_dev_token_here
# Production environment
MEETZY_API_TOKEN=your_prod_token_here
Using API Tokens
Include your API token in the Authorization header of your requests:
curl -H "Authorization: Bearer your_api_token_here" \
https://api.meetzy.ai/v1/assistants
Code Examples
const headers = {
'Authorization': `Bearer ${process.env.MEETZY_API_TOKEN}`,
'Content-Type': 'application/json'
};
fetch('https://api.meetzy.ai/v1/assistants', { headers })
.then(response => response.json())
.then(data => console.log(data));
import os
import requests
headers = {
'Authorization': f'Bearer {os.getenv("MEETZY_API_TOKEN")}',
'Content-Type': 'application/json'
}
response = requests.get('https://api.meetzy.ai/v1/assistants', headers=headers)
data = response.json()
curl -X GET \
-H "Authorization: Bearer $MEETZY_API_TOKEN" \
-H "Content-Type: application/json" \
https://api.meetzy.ai/v1/assistants
Managing Existing Tokens
Your token list displays:
- Token Name - The descriptive name you assigned
- Masked Value - First 24 characters + masked remainder for identification
- Expiration Date - When the token will expire
- Status - Active/Expired indicator
Copying Token Values
Locate Your Token
Find the token you need in your token list
Click Copy Button
Hover over the token row and click the “Copy” button that appears
Verify Copy Success
The button will briefly show “Copied!” to confirm the action
You can only copy the full token value if you’ve just created it. For existing tokens, only the masked version is available for security.
Revoking Access
When you need to revoke a token:
Identify the Token
Locate the token you want to revoke in your token list
Click Delete Button
Hover over the token row and click the trash icon
Confirm Revocation
Confirm the action in the popup dialog
Update Your Applications
Remove or replace the revoked token in any applications using it
Revoked tokens stop working immediately. Make sure to update any applications or services using the token before revoking it.
Token Expiration Handling
Monitoring Expiration
- Check expiration dates regularly in the token manager
- Set calendar reminders before tokens expire
- Monitor your application logs for authentication errors
Renewal Process
Create New Token
Generate a new token before the old one expires
Update Applications
Replace the old token in your applications with the new one
Test Integration
Verify that your applications work with the new token
Revoke Old Token
Once confirmed working, revoke the expired/old token
Troubleshooting
Authentication Errors
If you receive 401 Unauthorized errors:
- Verify the token is correctly included in the Authorization header
- Check that the token hasn’t expired
- Ensure there are no extra spaces or characters in the token value
Token Not Working
- Confirm you’re using the complete token value
- Verify the token hasn’t been revoked
- Check that your account has the necessary permissions for the API endpoint
Rate Limiting
API tokens are subject to rate limits:
- Implement exponential backoff for retries
- Monitor response headers for rate limit information
- Consider caching responses when appropriate
