Beta & Early Access

API Alerts 2.0 is in open beta right now. This page tracks what’s available today, what the open beta unlocks, and how to turn it on.

Available today

These are live, public, and free to use on the current plans.

• Push notifications. Mobile app on iOS and Android. Sent to every member of the event’s channel.
• REST API. POST /event with an API key. See the API reference.
• CLI. Send events from your terminal or scripts.
• GitHub Actions. Get notified when workflows succeed or fail.
• Zapier (inbound). Use Zapier to send events into API Alerts.

SDKs

The 2.0 event model adds three new fields to the SDK send signature: title (short headline), event (routing key, e.g. payment.failed) and data (arbitrary JSON metadata, available to router templates as {{data.fieldName}}). These let you send richer events from code and route them via event routing without changing your wire format.

Released with the new fields:

• Go
• JavaScript
• Python
• Kotlin
• Java
• C#
• Swift
• Rust
• PHP
• Dart
• Ruby

The older single-message send() call keeps working in every SDK; the new fields are optional additions, not breaking changes.

In open beta

These are live now for anyone who opts in, behind a “beta” badge in the dashboard - no waitlist, no application. The 2.0 platform introduces routing and multi-destination delivery on top of push. We use the open beta to harden the destinations under real-world traffic before tagging 2.0 as GA.

• Event routing. Match events by glob pattern and forward them to multiple destinations.
• Email. Deliver alerts to team members via Amazon SES.
• SMS. Twilio-backed SMS to team members.
• WhatsApp. Twilio-backed WhatsApp delivery.
• Slack. OAuth app, channel picker, Block Kit messages.
• Discord. OAuth bot, channel picker, rich embeds.
• Webhooks. Forward events as JSON to any URL.
• Zapier (outbound). Trigger Zaps from your API Alerts events.
• Event Designer. Visual editor for customising how events render per destination.

A note on the mobile apps

The iOS and Android apps will get a follow-up update after the 2.0 platform release. Until then, events sent with the new fields are accepted and routed correctly; the mobile app just shows the existing message field on the event detail screen.

What’s coming in the mobile update:

• Show the new event fields. title, event, and data appear on the event detail screen alongside the existing message and tags.
• Deep linking to events. Tapping a push notification opens directly to that event’s detail screen instead of the home feed.
• Per-channel push preferences. Use the new push notification settings to control which channels notify you, separately from your device-level notification settings.
• General polish. Layout, navigation, and performance refinements across the feed and event detail screens.

Coming after 2.0

See the 2026 preview for the broader picture. Not part of the open beta but already in design or scoping:

• Microsoft Teams, Telegram, PagerDuty, OpsGenie destinations
• PostHog and Segment as outbound destinations (events forwarded to analytics platforms)
• Native inbound connectors (PagerDuty, GitHub, Sentry, UptimeRobot and more) so services other than Zapier can push events into API Alerts directly

Getting access

The open beta is live - no waitlist, no application. To turn it on:

1. Create a free workspace (the free tier is fine to start)
2. Opt into the beta from your workspace settings to unlock the 2.0 features
3. Follow @api_alerts for updates as more lands

The 2.0 features then show up behind a “beta” badge in your dashboard.

Stay updated

Open beta launch, new SDKs, and feature rollouts get posted to our fresh new X account, @api_alerts. Follow there for the play-by-play as 2.0 ships.