🚧
Management of admin API keys will be moving
As a part of integrating with Harness,admin API keys will soon be managed by general Harness systems. We recommend against creating any new integrations that manage admin API keys with this endpoint unless it is for a temporary purpose because Harness API endpoints will soon be available for creating and deleting admin API keys.
For admin API keys that were created using this Split Admin API endpoint, they also need to be deleted using this same endpoint.
The server_side and client_side SDK API keys will continue to be managed using this endpoint.
For more information, go to Before and After Guide: API for Split Admins. You can also contact us at support@split.io and we will be happy to guide you to the best path forward.

Access requirements

The Authorization Bearer (Admin API Key authorizing the request) must have one of the following roles and scopes:

Admin API Key roles accepted

API_ALL_GRANTED
API_APIKEY

Admin API Key scopes accepted

GLOBAL

To learn more about Admin API Key roles and scopes, see API keys overview.