Changelog

eu.api.speechify.ai and us.api.speechify.ai pin the region that runs synthesis

Two new hosts serve the text-to-speech and voice endpoints from one region: eu.api.speechify.ai from Europe and us.api.speechify.ai from US East. api.speechify.ai is unchanged and stays the default.

• Only the base URL changes. The same API key, requests and responses work on every host.
• A model with no capacity in the region still runs. The request goes to the nearest pool that serves the model, usually US East.
• Not data residency. Your account, keys, voices, usage and logs stay in the United States on every host.
• Rate and concurrency limits are counted per region. Spend limits, project budgets and your credit balance count spend from every region.

No API version change is needed. See Regions.

api.sws.speechify.com stops serving on 19 January 2027

api.speechify.ai is the only production host for the SpeechifyAI API. The legacy host api.sws.speechify.com keeps answering until Tuesday 19 January 2027 at 14:00 UTC. From then, every request to it gets a 308 Permanent Redirect to the same path on api.speechify.ai. This replaces the 19 February 2026 entry, which said the legacy host was not being deprecated.

• Change your base URL to https://api.speechify.ai. The same API keys, requests and responses work there.
• Using an official SDK? Upgrade it or remove the hard-coded base URL. Our SDKs have defaulted to api.speechify.ai since February 2026.
• An integration still on the legacy host stops working on that day. Most HTTP clients either do not follow a redirect on a POST or drop the Authorization header when the redirect goes to another host.
• Responses from the legacy host carry Deprecation and Sunset headers with the date, so an API gateway or SDK that reads them can warn you.

Workspaces that called the legacy host in the last 30 days get an email, and a reminder 30 days before the date.