# /internal/api/v2/restrictions is deprecated

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

Split Admin API endpoints under /internal/api/v2/restrictions* are deprecated without a shutdown date. On your migration date, these endpoints will be disabled and calls to them fail as they are replaced with new endpoints on the Harness platform.

## What to use instead

Grant project view permissions using Harness role assignments and resource groups via the Harness Platform API with an x-api-key header. This move requires more than changing an identifier, as the replacement endpoints require creating a new Harness API key credential.

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

- API: Split Admin API (api.split.io)
- Kind: Endpoint removal
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/internal/api/v2/restrictions*`
- Source: [Announcement](https://developer.harness.io/feature-management-experimentation/troubleshooting-and-resources/split-to-harness-migration/migrate-from-split-to-harness/api-updates)
- Verified: November 6, 2026, against Split Admin API's own pages
- Page: https://www.okapi.bot/providers/split-admin-api/breaking-changes/internal-api-v2-restrictions-is-deprecated/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent