canonical: https://jentic.com/apis/split.io/split # Split Admin API Split.io is a feature flagging and experimentation platform. The Admin API provides programmatic access to manage feature flags (splits), environments, segments, users, workspaces, and API keys. The API exposes 17 endpoints secured with bearer authentication. ## For AI agents Programmatically create a feature flag (split), list feature flags (splits). Covers 17 operations with bearer authentication. ## Scope Does not handle payments, communications, or crm - use for marketing only. ## Capabilities - Create a feature flag (split) - List feature flags (splits) - Get a feature flag - Delete a feature flag - Update split definition for an environment - Kill (disable) split in environment ## Use cases ### Marketing Operations Use the Split Admin API to perform marketing operations programmatically. The API provides 17 endpoints covering core functionality including create a feature flag (split), list feature flags (splits), get a feature flag. Example prompt: Call POST /splits/ws/{workspaceId} to create a feature flag (split) ### Automated API Keys Management Automate API keys operations by combining multiple Split Admin API endpoints. Agents can list feature flags (splits) and then get a feature flag in a single workflow. Example prompt: Call GET /splits/ws/{workspaceId} to list feature flags (splits), then verify the result ### AI Agent Integration via Jentic AI agents discover and call Split Admin API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually. Example prompt: Search Jentic for 'create a feature flag (split)', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /splits/ws/{workspaceId} | Create a feature flag (split) | | GET | /splits/ws/{workspaceId} | List feature flags (splits) | | GET | /splits/ws/{workspaceId}/{splitName} | Get a feature flag | | DELETE | /splits/ws/{workspaceId}/{splitName} | Delete a feature flag | | GET | /splits/ws/{workspaceId}/{splitName}/environments/{environmentName} | Get split definition for an environment | | PUT | /splits/ws/{workspaceId}/{splitName}/environments/{environmentName} | Update split definition for an environment | | DELETE | /splits/ws/{workspaceId}/{splitName}/environments/{environmentName} | Kill (disable) split in environment | | POST | /segments/ws/{workspaceId}/environments/{environmentName} | Create a segment | ## Key resources - **API Keys** — Operations related to API Keys - **Environments** — Operations related to Environments - **Segments** — Operations related to Segments - **Split Definitions** — Operations related to Split Definitions - **Splits** — Operations related to Splits ## Why Jentic - **Setup:** Wiring the Split Admin API by hand means implementing its bearer auth and pointing every call at the api.split.io/internal/api/v2 host yourself. Through Jentic you install once, import the Split Admin API from the API Directory, store the admin token once, and your agent calls it. - **Permission scoping:** Split puts the workspace id in the URL path (/splits/ws/{workspaceId}/...), so a rule can pin your agent to one workspace and the feature-flag reads within it. You choose the operations it may call, so destructive ones like deleting a split or a split environment are not included unless you add them. - **Credential handling:** Your Split admin token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a feature flag' or 'list splits in a workspace', and Jentic returns the matching Split Admin API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Mailchimp** — Alternative marketing API - **Hubspot** — Alternative marketing API ## FAQ ### What authentication does the Split Admin API use? The Split Admin API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I create a feature flag (split) with the Split Admin API? Yes. Use the POST /splits/ws/{workspaceId} endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Split Admin API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I create a feature flag (split) through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a feature flag (split)'. Jentic returns the matching Split Admin API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Split Admin API have? The Split Admin API exposes 17 endpoints covering API keys, environments, segments operations. ### Can I limit what my agent is allowed to do with the Split Admin API? Yes. Because you run Jentic One yourself, your own rules decide which Split Admin API operations and credentials the agent may use. Since Split puts the workspace id in the URL path (/splits/ws/{workspaceId}/...), you can pin the agent to a single workspace and to read-only calls like listing or fetching feature flags within it. Destructive operations such as deleting a split or killing a split in an environment stay off limits unless you explicitly allow them.