Expo Push Service
expo.dev
- Free plan
- Web
- iPhone and iPad
- Android
- API
7.2 Club score Visit expo.dev
Plans
Every plan and priceExpo Push Service
Free
Free plan
What the maker publishes
- API batching
- A request may include up to 100 message objects, all for the same project. source
- Delivery guarantees
- Delivery is best effort; its infrastructure is designed for at-least-once handoff, which can occasionally result in duplicate or undelivered notifications. source
- Founded
- 2015 source
- Integrations
- The service passes notifications onward to Google FCM and Apple APNs. source
- Payload retention
- Notification contents are held in memory and message queues, not databases, and are not stored longer than delivery to Google and Apple. source
- Platform support
- Expo Push Service sends notifications to Android and iOS push notification services. source
- Purpose
- Expo simplifies implementing push notifications by handling much of the communication with Firebase Cloud Messaging and Apple Push Notification Service. source
- Push token data
- Expo stores push tokens needed to send notifications and deletes payloads after they are sent to FCM or APNs. source
- Rate limit
- The documented sending limit is 600 notifications per second per project. source
- SDK integrations
- Expo documents server SDKs for Node.js, Python, Ruby, Rust, Symfony, PHP, Golang, Elixir, .NET, Java, and Laravel. source
- Server sending
- Apps send notifications by making an HTTPS POST request to the Expo API using an Expo push token. source
- Service level
- The Expo Push Service does not offer an SLA. source
- Tool for testing
- Expo provides a web push notification tool for testing messages with tokens and fields including title, body, data, TTL, and platform-specific options. source
- Transport security
- Expo says its connections to Apple and Google use HTTPS encryption. source
Checked against the maker's pages on 14 Nov 2026.