Sinch: Sinch Engage - HTTP support for Sinch Engage APIs ends
Affected components: API, SMPP, webhooks, email to SMSSinch Engage - API, SMPP, webhooks, email to SMS
Timeline of updates
- scheduled
We are writing to inform you that after 30 October 2026, Sinch Engage will no longer accept API requests sent over HTTP.
If your integration connects using http:// URLs, you'll need to change them to https:// before then. It's a small change: your API, credentials and integration logic all stay the same.
More information about the change can be found here: https://support.app.sinch.com/hc/en-us/articles/17805834983311-Announcing-the-end-of-HTTP-support-for-Sinch-Engage-APIs (opens in new tab)
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-25 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
63fc3a55e0b6d8c3…
Impact, status and times are the vendor’s own, as last archived. View on status.sinch.com (opens in new tab).
Cite this
Maintenance posted by Sinch, started 2026-10-30 11:00 UTC, not resolved, 1 update(s).
- Title
- Sinch Engage - HTTP support for Sinch Engage APIs ends
- Vendor
- Sinch
- Date
- URL
- https://rewindex.com/company/sinch/incidents/n50m8bx2hnmv
Sinch profileRecent Sinch incidentsAll outages on October 30, 2026Sinch in October 2026MarkdownJSON