Mike Miller
December 13, 2024

Table of contents
We’re excited to confirm that Courier customers are unaffected by this update. Notifications sent via APNS with P8 keys or P12 certificates work seamlessly, and no changes are required.
Read more about what we tested
Apple is updating its Push Notification service (APNs) certificates to use the USERTrust RSA Certification Authority (SHA-2 Root). Key dates include:
To keep push notifications working, you must update your server’s Trust Store to include the new certificate authority. Both old and new certificates should remain trusted during the transition. Read Apple’s official announcement here.
We’ll update this post with details for `node-apn` and similar packages after January 20. Be sure to bookmark this post!
Courier has already implemented these changes, so you don’t need to worry. Notifications will flow seamlessly with no extra work on your part. Courier also lets you design and manage notification templates effortlessly. Explore Courier’s resources to get started:
If you are not using Courier, here's what you need to do:
If you’re updating manually, follow these steps:
Get the USERTrust RSA Certification Authority (SHA-2) certificate from Apple’s official site or a trusted source.
Unix/Linux Servers:
ca-certificates directory (e.g., /etc/ssl/certs/).Copied!
sudo cp /path/to/USERTrustRSA.crt /etc/ssl/certs/
Copied!
sudo c_rehash
Windows Servers:
If you’re using .p8 keys for APNs authentication, no changes are required for your app’s code. However, you still need to:
Skipping these updates may cause:
By preparing now, you’ll ensure your push notifications continue without interruption. If you need help, consult Apple’s documentation or contact your notification provider. Let’s make 2025 a seamless year for your app’s notifications!

Terminal-First Development vs. IDE: Building Notification Infrastructure with Claude Code and Cursor
AI coding tools split into two camps: terminal agents (Claude Code) and IDE-augmented editors (Cursor). This guide compares both approaches using Courier's CLI and MCP server as the test case. Covers installation, configuration, and practical workflows for building multi-channel notifications. Includes code examples for user management, bulk operations, and automation triggers. Also explores agent-to-agent communication patterns where AI systems need notification infrastructure to coordinate tasks and escalate to humans.
By Kyle Seyler
January 29, 2026

The Notification Platform Developers Choose
Most notification platforms built dashboards first and added developer tools later. Courier did the opposite. With a CLI that handles real workflows, MCP integration with setup management, typed SDKs in seven languages, and SOC 2 Type 2 certification, Courier is built for teams that ship. This isn't marketing copy: Twilio chose Courier to unify notifications across their 10M+ developer platform. LaunchDarkly uses Courier to power feature release workflows. When the companies that build developer infrastructure choose your notification platform, that says something about the technical foundation.
By Kyle Seyler
January 26, 2026

Vibe Coding Notifications: How to Use Courier with Cursor or Claude Code
Courier's MCP server lets AI coding tools like Cursor and Claude Code interact directly with your notification infrastructure. Unlike Knock and Novu's MCP servers that focus on API operations, Courier's includes embedded installation guides for Node, Python, Flutter, React, and other platforms. When you prompt "add Courier to my app," your AI assistant pulls accurate setup instructions rather than relying on outdated training data. OneSignal's MCP is community-maintained, not official. Courier supports 50+ providers, native Slack/Teams integration, drop-in inbox and preference components, and a free tier of 10,000 notifications/month. Configure in Cursor with "url": "https://mcp.courier.com" and "headers": { "api_key": "YOUR_KEY" }.
By Kyle Seyler
January 22, 2026
© 2026 Courier. All rights reserved.