Atlassian: Confluence
- REST API v1
- REST API v2
Vendor coverage
Atlassian API changes & breaking changes
Jira and Confluence Cloud expose several REST APIs each, with deprecations announced on a rolling basis and a migration from Confluence v1 to v2 still in progress. Detektu watches all of the published contracts.
Coverage
What Detektu monitors
Official products and contracts checked for changes.
Atlassian: Jira
- Jira Cloud Platform API
- Jira Software Cloud API
- Jira Service Management Cloud API
Change model
How Atlassian ships changes
The release patterns that shape your integration risk.
Atlassian ships Jira Cloud as three API surfaces (platform, software, and service management) and Confluence Cloud with both v1 and v2 REST APIs. Deprecations typically come with a six-month notice, announced in changelogs that are easy to lose track of across products.
Detektu diffs each contract independently and reports findings per product, so a deprecation in the Jira platform API doesn't blur into Confluence noise. The v1-to-v2 Confluence migration is a steady source of deprecations worth tracking structurally rather than by newsletter.
From change to finding
Findings you'd see
Illustrative examples. Every real finding carries exact before/after evidence, severity, and source provenance.
Confluence v1 content endpoint deprecated in favor of v2
openapi:GET /wiki/rest/api/contentField removed from a Jira platform search response
openapi:GET /rest/api/3/search ::response.200.namesMonitored for you
Do Atlassian's changes affect your integration?
Choose the operations and fields your services use. Detektu matches Atlassian findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.