API Tokens

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

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

JavaScript
Python
cURL

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

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

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

Connecting via MCP

Meetzy exposes a Model Context Protocol (MCP) server that gives AI assistants like Claude, Cursor, Windsurf, and ChatGPT direct, authenticated access to your calls, WhatsApp conversations, evaluations, and analytics — all using the same API tokens described above.

All data exposed through the MCP server is scoped to the account that owns the token. A token from your account can only read and act on that account’s assistants, calls, and conversations — there is no cross-account data access.

Getting the MCP Server URL

Open the MCP Section

Scroll to the “Connect via MCP” section at the bottom of the API Tokens page

Copy the Server URL

Click the copy icon next to the MCP server URL to copy it to your clipboard

Have a Token Ready

Use an existing API token, or create a new one, to authenticate your MCP connection

The MCP server URL alone does not grant access. Every request must include a valid Bearer token in the Authorization header, exactly like any other Meetzy API call.

Connecting Cursor, Claude, or Windsurf

These clients (and most desktop MCP clients) are configured through a JSON snippet that defines the server URL and headers. Add the following to your client’s MCP configuration file:

{
  "mcpServers": {
    "meetzy": {
      "url": "https://mcp.meetzy.ai",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}

Cursor
Claude Desktop
Windsurf

Open Settings → MCP, click “Add new MCP server”, and paste the JSON snippet above into the configuration editor. Replace YOUR_API_TOKEN with your actual token, then save and reload Cursor.

Open your claude_desktop_config.json file and add the meetzy entry under mcpServers, using the snippet above. Restart Claude Desktop for the new server to appear in your tools list.

Click Copy Configuration

Use the “Copy” button next to the JSON snippet in the token manager to copy a ready-to-use configuration

Replace the Placeholder Token

If you copied the snippet before creating a token, replace YOUR_API_TOKEN with your real token value

Paste into Your Client

Add the snippet to your client’s MCP configuration file as described above

Restart the Client

Restart or reload the application so it picks up the new MCP server

Connecting ChatGPT as a Custom Connector

ChatGPT supports MCP servers through Custom Connectors, authenticated with a Bearer token rather than a JSON config file.

Open Connector Settings

In ChatGPT, go to Settings → Connectors → Advanced → Custom Connectors

Add a New Connector

Click “Add custom connector” and give it a name, such as “Meetzy”

Enter the Server URL

Paste the MCP server URL from the token manager into the connector’s URL field

Set Authentication to Bearer Token

Choose Bearer Token as the authentication method and paste your API token as the value

Save and Enable

Save the connector, then enable it in your conversation to let ChatGPT call Meetzy tools

ChatGPT sends the Bearer token in the Authorization header on every request, so you can reuse the same token you use for direct API calls or other MCP clients.

Generic Connection (Any MCP-Compatible Client)

The Meetzy MCP server implements the Streamable HTTP transport, so any MCP-compatible client can connect to it directly without special integration work. All you need is:

Server URL: the MCP endpoint shown in the token manager
Transport: Streamable HTTP
Authentication: Authorization: Bearer <your_api_token> header on every request

curl -X POST https://mcp.meetzy.ai \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","method":"tools/list","id":1}'

{
  "url": "https://mcp.meetzy.ai",
  "transport": "streamable-http",
  "headers": {
    "Authorization": "Bearer YOUR_API_TOKEN"
  }
}

Do not hardcode your API token inside shared or version-controlled MCP configuration files. Use environment variable substitution where your MCP client supports it.

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

MCP Connection Issues

Make sure your MCP client supports the Streamable HTTP transport
Confirm the Authorization header is being sent on every request, including the initial handshake
If a tool call returns no data, verify the token belongs to the account that owns the assistants or calls you’re trying to access

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

Getting Started

Agents

Advanced Editor

Voice Library

Calls

CRM

Account

Accessing Token Manager

Creating a New Token

Token Security Best Practices

Storage Guidelines

Access Control

Environment Separation

Using API Tokens

HTTP Headers

Code Examples

Managing Existing Tokens

Viewing Token Information

Copying Token Values

Revoking Access

Token Expiration Handling

Monitoring Expiration

Renewal Process

Connecting via MCP

Getting the MCP Server URL

Connecting Cursor, Claude, or Windsurf

Connecting ChatGPT as a Custom Connector

Generic Connection (Any MCP-Compatible Client)

Troubleshooting

Authentication Errors

Token Not Working

MCP Connection Issues

Rate Limiting

​Accessing Token Manager

​Creating a New Token

​Token Security Best Practices

​Storage Guidelines

​Access Control

​Environment Separation

​Using API Tokens

​HTTP Headers

​Code Examples

​Managing Existing Tokens

​Viewing Token Information

​Copying Token Values

​Revoking Access

​Token Expiration Handling

​Monitoring Expiration

​Renewal Process

​Connecting via MCP

​Getting the MCP Server URL

​Connecting Cursor, Claude, or Windsurf

​Connecting ChatGPT as a Custom Connector

​Generic Connection (Any MCP-Compatible Client)

​Troubleshooting

​Authentication Errors

​Token Not Working

​MCP Connection Issues

​Rate Limiting

Accessing Token Manager

Creating a New Token

Token Security Best Practices

Storage Guidelines

Access Control

Environment Separation

Using API Tokens

HTTP Headers

Code Examples

Managing Existing Tokens

Viewing Token Information

Copying Token Values

Revoking Access

Token Expiration Handling

Monitoring Expiration

Renewal Process

Connecting via MCP

Getting the MCP Server URL

Connecting Cursor, Claude, or Windsurf

Connecting ChatGPT as a Custom Connector

Generic Connection (Any MCP-Compatible Client)

Troubleshooting

Authentication Errors

Token Not Working

MCP Connection Issues

Rate Limiting