Live

Sinch Conversation API – Removal of Batch API v1alpha and v1beta endpoints

MaintenanceOfficial update

Dear Client, On 16 December 2026, Sinch will remove the deprecated v1alpha and v1beta endpoints for the Conversation Batch API across all regions. Requests to these endpoints will fail after removal. Type: Planned maintenance Start time: 16 December 2026, 09:00 UTC End time: 16 December 2026, 13:00 UTC Action required: If your integration uses v1alpha or v1beta, update and test your requests against the corresponding v1 endpoints before maintenance begins. For example, the US endpoint for sending batch messages is https://us.conversationbatch.api.sinch.com/v1/projects/{project_id}/messages. The v1 endpoints will remain available. If you already use v1, no action is required. Please contact support@sinch.com should you require further information or assistance.

The latest update from Sinch.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Sinch

Scheduled

Dear Client, On 16 December 2026, Sinch will remove the deprecated v1alpha and v1beta endpoints for the Conversation Batch API across all regions. Requests to these endpoints will fail after removal. Type: Planned maintenance Start time: 16 December 2026, 09:00 UTC End time: 16 December 2026, 13:00 UTC Action required: If your integration uses v1alpha or v1beta, update and test your requests against the corresponding v1 endpoints before maintenance begins. For example, the US endpoint for sending batch messages is https://us.conversationbatch.api.sinch.com/v1/projects/{project_id}/messages. The v1 endpoints will remain available. If you already use v1, no action is required. Please contact support@sinch.com should you require further information or assistance.

Affected components

2
Batch APIConversation API - Batch API

Sinch in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

66

Days with an incident

49

Median duration

2 h 54 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

8 days
median 2 h 54 min
90 days agoToday

Other Sinch incidents

All incidents

Follow Sinch

Your coding agent knows when Sinch is down, and tells you when a failure is theirs, not yours. You can also get Sinch incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "sinch" and tell me if Sinch has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=sinch
Slack
/feed subscribe https://outages.live/feed.xml?providers=sinch

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane