API sunsets · Twilio · checked

Twilio Notify API v1 end of life on 31 January 2027

Twilio Notify API v1 reaches end of life on 31 January 2027. Twilio's own pages disagree on the date: the changelog, 23 January 2024, says 31 December 2025. The counts here run to 31 January 2027, from the help-centre article (last edited 9 July 2025): the later date, on the more recently edited page. Both pages were still published on 10 October 2026, and 31 December 2025 has passed. After it, every request to the Notify API fails. The failure is loud: calls return errors. Twilio names Bulk Messaging API as the replacement (for bulk SMS, and in public beta with no SLA on 10 October 2026; for push notifications, Twilio's Notify docs point to a Push API private beta sign-up). Record your real calls on v1 before the date and replay them on Bulk Messaging API: after it, nobody can record what v1 returned. Find every place your code pins v1: npx --allow-remote=root https://agentwares.vercel.app/dl/api-sunset-0.1.0.tgz scan

$ npx --allow-remote=root https://agentwares.vercel.app/dl/api-sunset-0.1.0.tgz scan

npx --allow-remote=root https://agentwares.vercel.app/dl/api-sunset-0.1.0.tgz scan lists every API version your code and config pin (Shopify, Meta Graph, Google Ads, HubSpot, Stripe and the rest of this list) with its end date, what breaks and this page's link. It needs no account and no API key, reads your files on your machine and sends nothing; its one request fetches this data. Free and MIT licensed.

The facts

API
Twilio Notify APICovers notify.twilio.com/v1 (Services, Bindings, Notifications, Credentials), called directly or through a Twilio SDK.
Version
v1
Ends
31 January 2027Twilio's own pages disagree: the changelog, 23 January 2024, says 31 December 2025. The counts here run to 31 January 2027, from the help-centre article (last edited 9 July 2025): the later date, on the more recently edited page. Both pages were still published on 10 October 2026, and 31 December 2025 has passed.
After the date
calls fail
Silent?
No: calls return errors
Replacement
Bulk Messaging APIfor bulk SMS, and in public beta with no SLA on 10 October 2026; for push notifications, Twilio's Notify docs point to a Push API private beta sign-up

What breaks after 31 Jan 2027

How to upgrade

  1. Find every place your code and config pin v1: npx --allow-remote=root https://agentwares.vercel.app/dl/api-sunset-0.1.0.tgz scan prints each file and line, and the variable name for a .env file, never its value.
  2. Read what changed between v1 and Bulk Messaging API in Twilio's notes, and list the calls that touch it.
  3. Before 31 January 2027, send your real calls to v1 and to Bulk Messaging API and compare the answers: same status, same fields, same values where they should match; after it, nobody can record what v1 returned.
  4. Change the version string, deploy, and watch the first day's responses.

Record your real calls on the old version before the date, and replay them on the new one.

agentcheck runs scheduled checks of an endpoint. A check sends the request you define (a path or a full URL, a method and a body, with your API key as a header, stored encrypted) on a schedule and compares each response with a golden: exact text, contains, a regular expression or a JSON Schema, none of which costs an LLM call. When a response stops matching, it opens an incident and alerts you. Point one check at v1 and one at Bulk Messaging API with the same golden, and you see which of your calls answer differently before 31 January 2027.

Set up the two checks, free

Free: 1 monitored target, hourly checks, badge and public status page. Starter: 3 targets, 5-minute checks, Slack and Discord alerts, 30-day history. Recording the calls your code already makes is a different path: the trace import (POST /api/v1/targets/{id}/traces, or the agentcheck_record MCP tool) takes agent traces, a prompt and an answer, and turns them into checks judged by the LLM judge (Pro). It does not take raw HTTP requests and responses, so for an API the scheduled checks are the way in today.

Migration watch is not built. It would record the calls your code makes to Twilio Notify API v1 and replay them on Bulk Messaging API until 31 January 2027, with nothing to set up, and email you what answers differently. If you would pay for that, say so with one click. The click is counted, and nothing else is sent or stored unless you then leave an email.

Other Twilio dates

Every API sunset, by date

Sources

Built only from Twilio's own pages. No intent is implied: a date is what the page says on the day it was read. Data: /apis/sunsets.json.

api-sunset is a free tool from agentcheck, which runs scheduled checks of your endpoints and alerts you when an answer changes.