AI Tools
The best free push notification API depends on who holds the phone
Website visitors call for free browser Web Push; personal ops scripts are simpler on a tiny trial ping API.
The best free push notification API depends entirely on who is holding the phone. If you want to notify website visitors at zero API cost, standard browser Web Push is the right answer. If you want to send server or script alerts to your own iPhone or Android without building an app, no hosted service gives unlimited free phone pushes forever, so the realistic pick is a tiny no-card trial like AyePing paired with a cheap annual cap once your script proves useful.
Match the tool to the recipient
| Recipient | Best free starting point | Why it fits | Real constraint |
|---|---|---|---|
| Website visitors | Browser Web Push (VAPID) | No per-message fee in major browsers | Needs HTTPS, service worker and user opt-in |
| Mobile app users | APNs and FCM directly | Official Apple and Google transport | Requires your own native app and backend |
| Yourself from a script | AyePing Free tier | One HTTP POST, existing phone app | Limited to 5 pings to try, then paid |
Splitting the question this way clears up most bad comparisons. A tool built for browser marketing will annoy an engineer paging themselves on disk space, and a personal ping token cannot broadcast to users.
What AyePing gives you free, and what costs money
As of November 2026, AyePing's Free plan asks for no card and gives 5 pings to try, 3 tokens and 90-day history in the iPhone and Android apps. It is strictly a test tier so you can prove the HTTP call works from curl, JavaScript fetch or Python urllib.request before spending anything.
If you keep using it, Hobby is $8 monthly or $49 billed yearly ($4.08 a month) for 120,000 pings a year and 25 tokens, and Pro is $20 monthly or $120 billed yearly ($10 a month) for 1,200,000 pings and 100 tokens. Both keep pings for a year, and unused pings do not roll over.
Why small safeguards matter on tight quotas
Even on a paid allowance, nobody wants a stuck loop to exhaust a year of alerts in ten minutes. According to AyePing's documentation, every token enforces an hourly cap between 1 and 3,600 requests (60 by default), returning HTTP 429 with rate_limited and a Retry-After interval when exceeded.
You can also attach Idempotency-Key (up to 255 characters) so network retries return the first ping's id rather than consuming quota twice, and you can pause any individual token (403 token_paused) without regenerating keys for other machines.
When staying 100% free makes sense
Stick with completely free routes when:
- Your volume is customer traffic: Web Push costs nothing per message and reaches anyone who accepts the browser prompt.
- You already manage a Linux box: Running your own push server leaves you with zero SaaS fees, trading server maintenance for no subscription bill.
- Alerts are non-urgent: Emailing yourself from a script costs nothing on small scales and leaves a searchable log.
A practical way to decide in ten minutes
Test the simplest option that matches your recipient. If you only want your phone to buzz when a script fails, spend your 5 free AyePing pings on a real staging check, verify the payload limits (32 KB body, 100-character title, 2,000-character Markdown message), and pick a paid tier only after the workflow proves its value.
FAQ
Is there an unlimited free API for iPhone push alerts?
Apple does not charge APNs fees per push, yet running APNs requires an iOS app and backend infrastructure. Hosted phone-app APIs restrict free plans (such as AyePing's 5 trial pings) because keeping apps in stores and relaying pushes costs real money.
Does AyePing read tracking pixels inside notification messages?
No. AyePing's docs state that images are not loaded in Markdown messages (only alt text is shown), so senders cannot see when you read a ping, and links prompt before opening.
What happens if a JSON payload exceeds 32 KB?
AyePing rejects requests larger than 32 KB with HTTP 413 (body_too_large) before parsing fields.