Authentication

Overview

All API requests require a valid API key in the Authorization header:

Authorization: Bearer YOUR_API_KEY

Without this header, requests return 401 Unauthorized.

Getting an API key

1. Sign in to the Speechify Console
2. Navigate to API Keys
3. Copy your default key, or create a new one

Authenticate the SDK

Set SPEECHIFY_API_KEY and let the SDK read it automatically, or pass the key explicitly:

1
from speechify import Speechify
2
3
# Reads SPEECHIFY_API_KEY from the environment
4
client = Speechify()
5
6
# ...or pass it explicitly
7
client = Speechify(api_key="your-api-key")

Make an authenticated request

A complete authenticated call — generated from our SDKs and the API spec, so the request (including the Authorization header in the cURL tab) stays in sync with the live endpoint:

1
curl https://api.speechify.ai/v1/voices \
2
     -H "Authorization: Bearer <token>"

Security best practices

Do

• Store keys in environment variables or secret managers
• Use server-side code to make API calls
• Add .env to your .gitignore
• Rotate keys periodically via the Console

Don’t

• Embed keys in client-side code (JavaScript bundles, mobile apps)
• Commit keys to version control, even in private repos
• Share keys over unencrypted channels

Platform-specific secret management

Server-side proxy pattern

If your frontend needs to call the API, set up a server-side proxy instead of exposing the key:

Client  →  Your Server (adds API key)  →  Speechify API

Key considerations:

• Create specific proxy endpoints (not a wildcard passthrough)
• Validate and sanitize inputs before forwarding
• Add rate limiting to prevent abuse

Error responses