API · SDK · runtime · authentication lifecycle intelligence

Last updated · 9 September 2026

SchemaTrace

Breaking changes, enforcement dates and migration requirements.

ST-2026-113 · API endpoints & versions

Atlassian retires Get users and Get groups organisation-directory endpoints

Atlassian deprecated the GET organisation-directory users and groups endpoints; they stop working after 30 June 2027 and are replaced by the v2 POST search endpoints.

AtlassianCloud Adminusers APIgroups APIv2

Previous state

Integrations could enumerate directory users and groups through GET /v2/orgs/{orgId}/directories/{directoryId}/users and GET /v2/orgs/{orgId}/directories/{directoryId}/groups.

Current state

The GET endpoints are deprecated and must be replaced with POST /v2/orgs/{orgId}/directories/{directoryId}/users/search and POST /v2/orgs/{orgId}/directories/{directoryId}/groups/search before they stop working after 30 June 2027.

Who needs to care

Atlassian Cloud Admin integrations that list organisation-directory users or groups through the deprecated GET endpoints.

What to do

Inventory both GET calls, migrate filters and pagination to the corresponding v2 POST search contracts and test before the cutoff.

What the source does not prove

This is separate from the June 2026 removal of older organization v1 APIs. The source says the two GET endpoints stop working after 30 June 2027; it does not move every directory API to POST.

Lifecycle history

Dated event sequence

  1. Deprecation and replacements announced

    Atlassian mapped the Get users and Get groups endpoints to the v2 search endpoints.

  2. Final supported date

    The deprecated GET endpoints stop working after this date.

Evidence ledger

First-party sources

  1. 01
    Atlassian Developer — Cloud Admin changelog

    Official API changelog · 2026-07-02

    Open official source ↗