groups* endpoint removal

Deprecated, no dateSubscribe to Split Admin APIShare

Split Admin API endpoints under /internal/api/v2/groups* are deprecated and will be disabled on your migration date without a universal shutdown date specified. After that date, calls to these endpoints fail as Split Admin API replaces them with new endpoints on the Harness platform.

Calls it hits

/internal/api/v2/groups*

What to use instead of these calls

Manage groups using the Harness Platform User Group API authenticated with a Harness API key in the x-api-key header. This move requires more than changing an endpoint, as you must create a new Harness API key credential.

The replacement endpoints are Harness Platform APIs that need a Harness API key, a new credential to create.

In Split Admin API's words

On your migration date, five Split Admin API endpoints will be disabled and replaced with new endpoints on the Harness platform.

Split Admin API, Announcement

Facts

API: Split Admin API api.split.io
Kind: Endpoint removal
Takes effect: No date given yet
Calls after that day: Fail
Source: Announcement
Last updated: October 25, 2026
Verified: November 6, 2026, against Split Admin API's own pages

Questions

When does this change take effect?

Split Admin API deprecated /internal/api/v2/groups* without giving a shutdown date yet.

Do these calls still work?

Yes, they still work: Split Admin API has not given a shutdown date yet.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

Is your code calling this?

Okapi finds the calls this change hits in your repo and opens the pull request with the fix.

Add to GitHub