Skip to content

[meta] API v4

This issue is meant to list all endpoints which are:

  • deprecated now and should be removed
  • duplicated and one will be removed
  • Behavioural change should happen
  • Exposed info will be hidden
  • Exposed field will be removed
  • etc etc

Please use the format like we do in regression issues.

API version change

In 8.17:

  • Add a v4 API version, which has all of the existing v3 endpoints and the changes in this issue that are ready before then. v3 is still the preferred API version, and v4 is beta.
  • Keep the v3 API around. If there was no change in v4, it can just use the same code as v4. If there was a breaking change, we need to have the old version available under v3 too, with the same behaviour as 8.17.
  • Add a page in the API docs listing all of these changes in one place, clearly saying that v4 is not done yet, and currently in beta.

In 9.0:

  • Ship all of v4, making it final and no longer beta
  • Deprecate v3
  • Tell the world that "v3 will continue to work until at least 9.2, but we will remove it at some point with no prior warning but a notice in the blogpost, and you should start upgrading your integrations now"

In 9.4 or later if there are good technical reasons:

  • Remove v3 endpoints and code.
  • Remove the API doc listing the changes.

Open issues

These are the open api && breaking change issues.

Tough nuts

These are quite a lot of work:

Quick wins

These should be easy/quick to tackle:

In between

These aren't really hard, but will take a bit more time:

Optional

These aren't actually breaking anything:

  • #28017 (closed) - API: Separate CE params to avoid wrong conflict resolutions
  • #20728 (moved) - Improve consistency in the way we retrieve project & group in API endpoints

Ongoing

These are already been working on:

Done

Current doc with V3 to V4 API changes