Split

Split (Harness FME) is a feature-flag and experimentation platform: flags are defined per project and rolled out per environment, targeting groups of keys called segments.

Authentication

• API key

Actions

Generic API request. Call any Split API endpoint on this connection, for the case where no shipped action covers it yet. The connection supplies the base URL, the authentication and the egress route, so only the path, query and body are yours to fill.

• Create feature flagCreate a feature flag under a traffic type (POST /splits/ws/{workspaceId}/trafficTypes/{trafficTypeId}).
• Get feature flagRead one feature flag's definition - description, trafficType (the unit it randomises on, e.g. user) and tags - addressed by workspaceId plus the flag's case-sensitive name rather than a generated id, so the name has to match exactly.
• List environmentsList the environments defined in one project (Split calls a project a workspace) - each with its id, name and a production flag - which is where the environmentId that environment-scoped calls such as List segments require comes from.
• List feature flagsList feature flag definitions in an environment (GET /splits/ws/{workspaceId}/environments/{environmentId}).
• List segmentsList the segments - named groups of keys used for targeting - defined in one environment of a project.
• List traffic typesList the traffic types defined in one project (Split calls a project a workspace) - the key kinds, typically user and account, that a feature flag is evaluated against - which is where the trafficTypeId that Create feature flag requires comes from.
• List workspacesList the projects (workspaces) for the account (GET /workspaces).

Product names, logos and brands are the property of their respective owners and are used here for identification only. Their use does not imply endorsement by, or affiliation with, those owners.