Split Admin API

Name: Split Admin API
Brand: Split Admin API
Availability: InStock

✓ Official Vendor SpecMarketingSeo Sembearer17 EndpointsREST

For Agents

Programmatically create a feature flag (split), list feature flags (splits). Covers 17 operations with bearer authentication.

Install Jentic One Beta

Connect the Split Admin API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Split Admin API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Split Admin API.

Create a feature flag (split)

List feature flags (splits)

Get a feature flag

Delete a feature flag

GET STARTED

Start building with Split Admin API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Split Admin API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'create a feature flag (split)', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

17 endpoints — split.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Split Admin API through Jentic.

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.

Split Admin API

Connect the Split Admin API to your agent

Capabilities

Start building with Split Admin API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs