Beta & Early Access

API Alerts is mid-roll-out of its 2.0 platform. This page tracks what’s actually available right now, what’s in closed beta, and how to get in.

Available today

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

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:

Will be updated for the open beta:

And new SDKs landing soon to round out the lineup for 2.0: Dart / Flutter, Java, PHP, and Ruby. Watch @api_alerts for announcements.

This page updates as each one lands. The older single-message send() call keeps working in every SDK; the new fields are optional additions, not breaking changes.

In closed beta

These are built and being validated with a small group of users. They are NOT yet open for self-signup. The 2.0 platform introduces routing and multi-destination delivery on top of push.

  • 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.

Public open beta

Target: early-to-mid June 2026. Everything currently in closed beta opens up for self-signup, behind a “beta” badge in the dashboard. We’re polishing off a few rough edges and making sure everything’s ready for the public. Same product, wider access. We use the open beta period to harden the destinations under real-world traffic before tagging 2.0 as GA.

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

Closed beta isn’t accepting new entrants right now. We’re polishing off the last rough edges with the existing testers before opening the gates.

The path forward is the public open beta in early-to-mid June, which drops the waitlist entirely. To be ready:

  1. Create a free workspace (the free tier is fine to start)
  2. Follow @api_alerts for the open beta launch announcement

The 2.0 features unlock in your dashboard the day open beta opens. No application, no email, no waiting in line.

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.