Migration: API Updates – Split Help Center

This article provides an update to information originally shared via email on 2/21/25 regarding changes to Split Admin API Endpoints & Migration to Harness. Going forward, we will publish further updates here as needed. Our goal is to provide one place to look regarding this topic going forward.

As of 2/26/25: The “GET workspaces” API endpoint is no longer on the list of impacted API endpoints. We are retaining this endpoint to make this transition easier for you, our customer.

As of 3/11/25: The Before and After Guide: API for Split Admins has been published.

What’s Changing for the Split Admin API?

On your migration date, five Split Admin API endpoints will be disabled and replaced with new endpoints on the Harness platform. This is part of the migration of user, group, project, project view permissions, and Admin API key management to Harness’s standard platform features. These enhancements will give you greater account control and visibility.

Important Note:

These changes to the Split Admin API do not affect your day-to-day feature flag evaluations within your applications.
The Split Admin API is optional, so these changes only impact you if you use it to query administrative data or automate administrative tasks outside of the Split UI.

Am I Impacted?

To help you determine if you need to take action, Harness took a sample of your Split Admin API usage between January 24 – February 19. We provided the results to all admins by email on Feb 21, 2025. We then made a change on Feb 26, 2025 to reduce the number of accounts impacted by 50%. These updated findings were sent to admins on Feb 27, 2025, and placed your account into one of four groups:

1. No use of impacted API endpoints found

We found no usage of the five impacted endpoints above in your account during the sample period. However, if you might only occasionally use these endpoints or were planning to start using them later, you may still be affected even though we did not detect such usage.

2. Use limited to GET workspaces endpoint found - no longer an impacted endpoint

Since the GET workspaces endpoint is no longer impacted and it was the only such endpoint we observed between 1/24/25 - 2/19/25, you no longer have an issue to resolve and your advice as of 2/27/25 is as follows:

3. Use of to-be-disabled GET (read only) endpoints found

We found some usage of these five endpoints in your account between January 24 – February 19. The API calls observed were all "GET" operations. GET calls are used to retrieve information from Split but not make administrative changes.

If you do not update your API interactions before your migration date, any external systems that rely on these endpoints (such as dashboards or reports) will no longer be able to retrieve data.

Additionally, if you occasionally use Split Admin API operations to make administrative changes—but did not do so during the observed period—your ability to automate those changes will be disrupted if updates are not made.

4. Use of endpoints that make changes found

We found significant usage of these five endpoints in your account between January 24 – February 19. The API calls observed included both:

Information Retrieval: Queries retrieving data from Split.
Administrative Actions: Operations making changes to your Split account.

If you do not update your API interactions before your migration date, you may experience:

Loss of Data Access: External systems (e.g., dashboards) relying on these endpoints will no longer be able to retrieve data.
Disruptions to Automated Updates: Any automated processes that modify users, groups, projects, or permissions will need to be updated to ensure continued functionality.

What to Do If Action Is Required

If your team has automation scripts that rely on any of these five Split Admin API endpoints, you’ll need to:

Update and test your automation to use the new Harness API endpoints before your migration date.
Be ready to switch to the updated code ON your migration day.

The impacted endpoints:

/apiKeys (Admin API Keys only—SDK API Key management remains unchanged)
/groups
/restrictions (Project View Permissions)
/users
/workspaces
- GET workspaces will remain available after migration
- POST, PATCH, and DELETE workspaces will be disabled upon migration

How We’ll Support You

Admin access to your new Harness account will be provided by [DATE TBD]
We released Before and After Guide: API for Split Admins on March 11th, 2025 to help you update your automation code. This Postman collection contains both working examples and background information to help you focus on just the endpoints and actions you need to learn.
Your CSM can provide a list of the specific endpoints and HTTP methods (GET, PUT, POST, PATCH, DELETE) used. However, they will not have access to request contents or know which of your scripts is calling them.

FAQs

Q: Do my developers need to update Split SDKs in our applications?
A: No, this change does not affect the APIs used by Split SDKs or infrastructure components like Split Proxy, Synchronizer, or Evaluator.

Q: Are all Split Admin APIs moving to Harness?
A: No, only the above Admin API endpoints related to Authentication and Authorization are migrating.

Q: Do I need to share this with all developers in my organization?
A: No, only with teammates who write or maintain admin automation code for managing users, groups, projects, and permissions in Split.

Q: Will I need a Harness API Key to use the new Harness endpoints?

A: Yes. This diagram shows which endpoints would need a Harness API Key.

Q: Where can I learn more?
A: Start with the Before and After Guide: API for Split Admins. Also have a look at Split to Harness Migration Overview and 30 Seconds to Confidence: How Your Migration Will Work. Still have questions? please contact your CSM or support@split.io.