February 2026
New API endpoints for project management
Seven new API endpoints are now available to help you manage your projects directly through the API:For organization-scoped API keys:For project scoped API keys:Check out the Phare API documentation for all available endpoints.
Organization-scoped API keys
You can now create organization-scoped API keys. These keys provide access to all projects within your organization and allow full project management, including the ability to create and manage projects.Project-scoped API keys remain available and are still best for setups where projects must stay clearly separated, such as agencies or larger organizations.Organization-scoped API keys are ideal for small teams, startups, and infrastructure provisioning. Most API requests with these keys require a project selection header.
New API endpoints for incident management
Three new API endpoints are available to give you more possibilities to automate your incident workflows:Check out the Phare API documentation for all available endpoints.
More control over incident timing and history
Incidents can now be created with precise start and end times, and existing incidents can be adjusted if the original timing was off. This helps keep status pages accurate when something was detected late or when special circumstances change how an incident should be reported.It’s also now possible to choose what type of status page update should be published at creation time. This is just a shortcut: all update types can still be posted later if needed.
January 2026
SMTP ports now available for monitoring
SMTP ports can now be monitored like other services over TCP. The usual ports are supported: 25, 465, 587, and 2525, making it easier to keep an eye on your in-house mail servers.Improved webhook JSON editor
The JSON editor to customize outgoing webhook payloads now highlights valid placeholders and loop names, warns on invalid tokens, and suggests available entities and properties as you type.Editing is smoother too: new lines are pre-filled, error handling is clearer, and the editor can expand for large schemas.It’s like a small handcrafted IDE inside Phare 🌞
Outgoing webhook schema upgrades
Schemas now support loops, and the default schemas for every alert event have been revamped to expose richer data out of the box. The new placeholder syntax uses{{ entity.property }} and is documented in the Outgoing Webhooks docs.
Improved notification preferences
Important organization-level notifications are now sent to all admins, not just the organization owner. In addition, every user can opt out of individual notification types from personal settings.This removes the single-owner bottleneck while keeping you in control of what lands in your inbox.
Custom quota notification thresholds
Notification thresholds for billable quotas are now fully configurable. Instead of fixed alerts at 80% and 100%, each quota can trigger notifications at values that actually match how you monitor usage.This is useful if you want earlier warnings for critical quotas or fewer alerts for ones you don’t care about.
Legal and billing emails per organization
Organizations can now configure separate Legal and Billing email addresses. The legal email is used for privacy policy and terms of service updates, while the billing email receives invoices and other payment-related notifications.If your legal and finance departments are actually just you, feel free to send both emails to yourself and role-play.