Messaging and notifications is led by a service AWS stopped supporting on October 30

Messaging and notifications is led by a service AWS stopped supporting on October 30

The Messaging & Notifications use case covers transactional email, SMS and voice, push and in-app notifications, with templating, preferences and deliverability tracking. Most applications need this job, but the page lists only 4 providers and 8 APIs, the smallest of the 90 use cases in the taxonomy.

What the page lists

Provider Kin Score Band APIs
Amazon Pinpoint 83.3 exemplar 2
Novu 71.0 exemplar 1
Mailboxlayer 69.0 exemplar 2
AT&T 43.9 developing 3

Amazon Pinpoint ranks first, and its own catalog description includes the reason it should not: “AWS will end support for Amazon Pinpoint on October 30, 2026.” That date has passed. The note continues that SMS, voice, mobile push, OTP and phone number validation continue under AWS End User Messaging. A builder who starts from this page would therefore begin with a service that is already shut down.

The other entries have problems too. Mailboxlayer validates email addresses with syntax checks, MX lookup, SMTP verification and disposable-address detection. That helps deliverability, but it sends nothing. AT&T is a carrier holding company whose developer surface spans four programs. Novu is the only listed provider that does the whole job on the page: one REST API and a workflow engine that route a triggered event to in-app inbox, email, SMS, push and chat.

Who is missing

The providers you would expect here are all in the catalog, and none of them are on this page:

Provider Kin Score APIs
Twilio 90.3 55
SendGrid 87.3 44
OneSignal 78.0 2
Postmark 71.3 3
Vonage 64.1 22

Twilio and SendGrid each score higher than every provider the page lists. Twilio alone has 55 APIs, nearly seven times the page’s total of 8.

What is ours to fix

The page is built from use-case terms the pipeline extracts from each provider’s profile. This page matched only three raw terms: “In-App Messaging Integration”, “Transactional Email Hygiene” and “Transactional Notifications”. Its alias list is wider and includes “sms messaging”, “push notification”, “email delivery” and “chat messaging”, but those aliases have not pulled in the providers whose profiles describe exactly that work. Fraud detection, by comparison, matched 300 providers. This page is short because its matching is narrow, not because the market is small. An end-of-support flag should also lower a provider’s ranking on a page meant to help someone choose.

A build path today

Use Novu for routing and preferences. Put Twilio or Vonage behind it for SMS and voice, SendGrid or Postmark for email, and OneSignal for push. Use Mailboxlayer to clean addresses before you send. If you are on AWS, go to End User Messaging, not Pinpoint.

Takeaway

Before you trust a ranking, check the status of the provider at the top. The page is at apis.io/use-cases/messaging-notifications/.

← Japan and Korea sells itself on carmakers, and its leaders are a messenger and a payment API
Sift Stack's Rule Service API never deletes a rule; it files a POST you can undo →