Changelog
Notable platform and API changes, newest first. For machine-readable spec
revisions, track the OpenAPI info.version in
/openapi.json — it stamps every published
revision of the developer API.
Breaking changes are called out explicitly with migration notes. Additive changes (new endpoints, new optional fields, new response headers) are not breaking — write clients that tolerate unknown fields so they keep working as the surface grows.
How to track changes
- Spec version —
info.version(date-stamped, e.g.2026-06-17) increments when the developer API surface changes. Diff the spec to see exactly what moved. - Discovery —
/.well-known/oauth-authorization-serverreflects the current OAuth endpoint set; read it rather than pinning URLs. - This page — a human summary of the changes worth knowing about, seeded now and growing as the platform evolves.
Recent changes
API spec 2026-06-17
- App versioning endpoints published.
POST/GET /developer/clients/{clientId}/versions(and the moderator review endpoints) are now in the OpenAPI spec — submit a whole-app config snapshot for review instead of editing a live client in place. See App versioning.
Earlier revisions established the core surface: OAuth 2.0 + PKCE with refresh / revoke / introspect, OpenID Connect, dynamic client registration, the scoped data API (recipes / genes / reuse), recipe create + publish, webhooks, and the connected-apps and developer-program endpoints.
Related
- API overview — the current endpoint surface, rendered live from the spec
- App versioning — the most recent addition
- Support — how to get help and what diagnostics to include
- Status & SLA — service health and operational response targets
- Incidents — incident lifecycle, updates, and postmortems
- Follow along in the community discussions.