Skip to main content

Changelog

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

March 2026​

2026-03-19​

Multi-Project Accounts

  • Renamed workspaces to accounts — accounts are now the top-level billing and organizational unit
  • Added projects as isolated resource environments within accounts
  • Each account can have multiple projects (plan-dependent: Free=1, Starter=3, Pro=10, Scale=50, Enterprise=Unlimited)
  • Two-level role system: account roles (Owner, Admin, Billing Admin, Member) + project roles (Admin, Developer, Viewer)
  • Role cascade: account Owners/Admins automatically get Admin access to all projects
  • Project-scoped API keys, domains, messages, subscribers, webhooks, and templates
  • Per-project usage tracking with account-level billing rollup
  • Account and project avatars with 24 built-in icons

Account Abuse Prevention

  • Added per-user free account limit: each user can own a maximum of 2 free accounts
  • Added cross-account usage aggregation: usage across all accounts a user owns is summed and enforced against free-tier limits
  • Prevents abuse where users create multiple free accounts to circumvent plan limits
  • Enforcement applied to all channels: email, push, SMS, in-app, and MAU
  • Dashboard shows upgrade prompt when free account limit is reached

API

  • Added POST /v1/accounts — create new accounts (with free account limit enforcement)
  • Added GET /v1/accounts/me — get current account with plan and limits
  • Added PATCH /v1/accounts/me, DELETE /v1/accounts/me — update/delete account
  • Added account member management: list, invite, update role, remove
  • Added account invitation management: list, resend, revoke
  • Added GET /v1/accounts/me/projects — list projects for account
  • Added GET /v1/accounts/me/project-breakdown — per-project usage and resource breakdown
  • Added GET /v1/accounts/me/resource-counts — account-wide resource counts
  • Added project CRUD: create, list, get, update, delete
  • Added project member management: list, add, update role, remove
  • Added GET /v1/usage/user-aggregate — cross-account usage aggregation
  • Added POST /v1/usage/reconcile — manual usage reconciliation
  • Removed legacy /v1/workspaces endpoints

Documentation

  • Updated Postman collection: replaced Workspaces with Accounts, added Projects and Usage folders
  • Added Accounts & Projects guide with free account limits documentation
  • Updated Usage & Analytics guide with cross-account usage aggregation

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 account and project 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.