> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/api-reference/more-products-apis/fme-admin-api.md).

# FME Admin API (Legacy Split)

Manage feature flags, segments, environments, users, and change requests in Harness FME with the Admin API, formerly the Split API.

The FME Admin API (Legacy Split) is the original Split API for Harness Feature Management & Experimentation (FME). It manages projects, environments, feature flags, segments, traffic types, users, groups, and change requests, and it includes the Events API for sending events. This reference also covers the flag sets, large segments, and rule-based segments APIs. For the newer API, use [Feature Flags](https://developer.harness.io/api-reference/more-products-apis/feature-management-and-experimentation.md). For the classic Harness Feature Flags product, use [Feature Flags Classic](https://developer.harness.io/api-reference/more-products-apis/feature-flags-classic.md).

## Request basics

* **API key token**: Send an Admin API key, a Harness personal access token, or a service account token in the `Authorization: Bearer` header. Go to [Authentication](https://developer.harness.io/feature-management-experimentation/api/) to choose a credential type, and [Manage API keys](https://developer.harness.io/harness-platform/use-harness-platform/automation/api/add-and-manage-api-keys) to create a Harness token.
* **Project ID**: This API calls a project a workspace. Endpoints take it as a `workspace-id` path parameter, or a `wsId` query parameter. List your projects with `GET /workspaces` to find the ID.
* **Base URL**: Send requests to `https://api.split.io/internal/api/v2`, followed by the endpoint path. The flag sets, large segments, and rule-based segments endpoints use `https://api.split.io`, and the Events API uses `https://events.split.io/api`. The Events API takes an SDK API key in the `Authorization: Bearer` header instead of an Admin API key. Each endpoint page shows the base URL it uses.

## Example request

List the projects in your account:

```bash
curl "https://api.split.io/internal/api/v2/workspaces" \
  -H "Authorization: Bearer $ADMIN_API_KEY"
```

Set `ADMIN_API_KEY` to your API key token.

## Find an endpoint

Endpoint paths are relative to the base URL.

* **Projects and environments**: List projects with `GET /workspaces` and environments with `GET /environments/ws/{workspace-id}`. Create an environment with `POST /environments/ws/{workspace-id}`.
* **Feature flags**: List flags with `GET /splits/ws/{workspace-id}` and read one with `GET /splits/ws/{workspace-id}/{feature-flag-name}`. Read or change a flag's definition in an environment with `GET` and `PATCH /splits/ws/{workspace-id}/{feature-flag-name}/environments/{environment-id-or-name}`. Kill a flag with `POST` on the same path followed by `/kill`.
* **Flag sets**: Group flags so SDKs can load only the flags they need.
* **Segments**: Create and list segments with `POST` and `GET /segments/ws/{workspace-id}`. Add or remove keys in an environment with `PUT /segments/{environment-id}/{segment-name}/uploadKeys` and `PUT /segments/{environment-id}/{segment-name}/removeKeys`.
* **Large segments and rule-based segments**: Manage segments that hold many keys or that match users by rules instead of a list of keys.
* **Traffic types and attributes**: List traffic types with `GET /trafficTypes/ws/{workspace-id}`, and manage the attributes on a traffic type under `/schema/ws/{workspace-id}/trafficTypes/{traffic-type-id}`.
* **Identities**: Add, update, or delete the identities of a traffic type in an environment under `/trafficTypes/{traffic-type-id}/environments/{environment-id}/identities`.
* **Users, groups, and API keys**: Manage users with `/users`, groups with `/groups`, and Admin API keys with `/apiKeys`.
* **Change requests, restrictions, and rollout statuses**: List change requests with `GET /changeRequests`, approve or reject one with `PUT /changeRequests/{change-request-id}`, and list rollout statuses with `GET /rolloutStatuses`.
* **Events**: Send events to measure impact with `POST /events` for one event and `POST /events/bulk` for many, on the Events API base URL.

## Known behavior

* **Query strings**: Endpoints that take query parameters, such as `replace` on the segment upload endpoints and `wsId` on rollout statuses, list them as parameters. Do not add them to the path.
* **Legacy name**: The API and some response fields still use the Split name, such as `split` for a feature flag and `workspace` for a project.
