API changelog

Changes to the OpsMerge API are announced here, newest first. The promises behind each entry — what counts as breaking, and how much notice you get per stability tier — are on the API page. The spec's info.version is date-based and matches the most recent entry.

2026-06-11

Initial public API release.

• Per-key scopes — API keys can be restricted to exactly the feature areas and access levels an integration needs (family:level, e.g. agents:read, scripts:execute). Full access remains the default for keys that need it. See API → Scopes.
• Full surface documented — every endpoint is documented in the interactive reference at app.opsmerge.cloud/api/docs, generated from the OpenAPI spec and enforced against the live router in CI, so the docs cannot silently drift from reality.
• Stability tiers — every operation is marked stable, beta, or internal (the x-stability field in the spec). Build on stable; the tier definitions and our change-notice promises are on the API page.

Related

• API — authentication, scopes, rate limits, conventions
• API error codes — every machine-readable error code