Skip to main content

Changelog

Track changes to the Zyphr API, SDKs, and platform.

February 2026​

2026-02-06​

Documentation

  • Added auto-generated API reference from OpenAPI spec
  • Added Go and PHP integration guides
  • Added cURL examples for all API endpoints
  • Added Error Codes reference page
  • Added FAQ and troubleshooting guide
  • Fixed Python SDK docs (now a requests-based integration guide)
  • Added Postman collection documentation

January 2026​

2026-01-31​

Auth-as-a-Service

  • Launched Auth-as-a-Service feature set
  • Added auth applications management
  • Added end user management
  • Added magic link authentication
  • Added OAuth provider integration (Google, GitHub, Microsoft, Apple)
  • Added MFA support (TOTP, SMS, email, recovery codes)
  • Added security features (rate limiting, IP allowlists, session management)

API

  • Added 67 new auth endpoints under /v1/auth/
  • Added comprehensive webhook events for auth actions

Documentation

  • Added Auth-as-a-Service guide and feature documentation

2026-01-15​

Platform Launch

  • Launched Zyphr v1 API
  • Email channel (AWS SES)
  • Push notification channel (APNs, FCM, Web Push)
  • SMS channel (Twilio)
  • In-App Inbox with real-time WebSocket support
  • Template engine with Handlebars
  • Subscriber management with preferences
  • Topic-based pub/sub notifications
  • Webhook delivery with signature verification
  • Node.js SDK (@zyphr-dev/node-sdk)
  • React Inbox component (@zyphr/inbox-react)
  • Dashboard for workspace management

Versioning Policy​

The Zyphr API uses URL-based versioning (/v1/). We maintain backwards compatibility within a major version:

  • Additive changes (new endpoints, new optional fields) are made without version bumps
  • Breaking changes will be introduced in new versions (/v2/) with migration guides and a deprecation period
  • SDKs follow semantic versioning

Subscribe to the Status Page for uptime and incident notifications.