Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.meetzy.io/llms.txt

Use this file to discover all available pages before exploring further.

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:
1

Open Account Menu

Click on your profile avatar in the top-right corner of the dashboard
2

Select Account Settings

Choose “Account Settings” from the dropdown menu
3

Access Token Manager

Click on the “API Tokens” tab to view your token management interface

​
Creating a New Token

1

Click New Token

Click the “New Token” button in the token manager interface
2

Enter Token Details

Provide a descriptive name for your token (e.g., “Production API”, “Analytics Service”)
3

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
4

Generate Token

Click “Create Token” to generate your new API token
5

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

​
HTTP Headers

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));

​
Managing Existing Tokens

​
Viewing Token Information

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

1

Locate Your Token

Find the token you need in your token list
2

Click Copy Button

Hover over the token row and click the “Copy” button that appears
3

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:
1

Identify the Token

Locate the token you want to revoke in your token list
2

Click Delete Button

Hover over the token row and click the trash icon
3

Confirm Revocation

Confirm the action in the popup dialog
4

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

1

Create New Token

Generate a new token before the old one expires
2

Update Applications

Replace the old token in your applications with the new one
3

Test Integration

Verify that your applications work with the new token
4

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