Docs

API Documentation

Build powerful text-to-speech applications with our simple REST API. Generate audio asynchronously, stream it in real time, or integrate via MCP.

One unified API and TTS aggregation platform instead of stitching together provider-specific integrations. Access voices from Google Cloud/Gemini TTS, Amazon Polly, Kokoro, and more — with harmonized voice IDs, standard output formats, async jobs, safe retries, enterprise webhooks, and storage that scales with your plan. Also advanced features accessible including creating voice playlist sharing, bookmarks, library management with tags/collections and more.

Format:
Download OpenAPI Spec (JSON)
44/50
Request
{
  "text": "Hi there! Its a pleasure to have you here...",
  "voice_id": "google:en-US-Chirp3HD-Charon"
}

This docs playground is an anonymous demo, so it returns a temporary audio_url for direct playback. Real API v1 integrations should use the authenticated audio_endpoint from /api/v1/tts/{job_id} instead of depending on signed storage URLs.

Demo endpoint. Sign up for your API key.

Quickstart

Get started in 2 minutes

API Reference

Full endpoint documentation (46 endpoints)

Provider Capabilities

Feature support by provider and tier

Webhooks

Real-time job notifications

Examples

Code samples in multiple languages

MCP

Connect AI assistants via Model Context Protocol

Base URL

https://aitts.theproductivepixel.com/api/v1

Authentication

Public v1 REST requests accept an API key or OAuth access token in the Authorization header:

Authorization: Bearer tts_your_api_keyAuthorization: Bearer oauth_at_your_access_token

Response Format

All responses are JSON with success boolean and data or error object.

Authentication Models

Public v1 REST endpoints support either credential in the Authorization header:

  • API Key: used for REST API calls such as generation, polling, audio retrieval, voice listing, and usage. Create keys from your Dashboard under the API tab. Keys start with tts_ and are passed via the Authorization: Bearer header.
  • OAuth access token: used for the same public v1 REST endpoints when issued with the required scopes. OAuth tokens start with oauth_at_ and use theAuthorization: Bearer header.
  • Firebase ID Token: used only for account and webhook management endpoints. Obtain a token by signing in with Firebase Auth, then pass it as a Bearer token in the Authorization header. It is not accepted for public v1 REST generation, status, or audio retrieval.

Frequently Asked Questions

Need help? Contact support

© 2026 AI TTS Microservice. All rights reserved.