canonical: https://jentic.com/apis/getunleash.io/getunleash

# Getunleash Admin API

Jentic publishes the only available OpenAPI specification for Admin API, keeping it validated and agent-ready. The Unleash Admin API is the management surface of the Unleash feature flag platform. Across 10 endpoints it covers addons (third-party integrations), API tokens, archived feature flags, and admin insights, allowing platform engineers to provision integrations, mint new SDK tokens, and manage the lifecycle of retired flags. Authentication is an apiKey supplied via the Authorization header.

## For AI agents

Provision Unleash addons, manage API tokens, and control archived feature flags through the Unleash Admin API across 10 endpoints with header-based key auth.

## Scope

Does not handle flag evaluation in client SDKs, billing, or user account management - use for Unleash admin operations on addons, tokens, and archived flags only.

## Capabilities

- Provision Unleash addons such as Slack, webhooks, and Jira integrations
- Mint new API tokens scoped to specific Unleash projects or environments
- Archive obsolete feature flags or revive them by name
- Query admin insights such as flag counts and integration health
- Update an existing addon configuration in place rather than recreating it
- Delete an addon when an integration is removed from the workflow

## Use cases

### Provision Feature Flag Integrations from CI

Platform teams provision Unleash addons such as Slack notifications or Jira links from a CI pipeline so each new project gets the same integration set without manual UI clicks. The POST /api/admin/addons endpoint accepts the integration payload and returns the created addon record. Update and delete endpoints allow lifecycle management as the integration set evolves.

Example prompt: Create an Unleash Slack addon configured to post to channel '#deploys' on flag-changed events.

### Token Lifecycle for SDK Bootstrapping

When a new service starts using Unleash it needs an SDK API token scoped to the right project and environment. POST /api/admin/api-tokens creates the token and GET /api/admin/api-tokens lists existing tokens so platform tooling can rotate or revoke credentials on schedule, without sharing master keys with each team.

Example prompt: Mint a new Unleash API token for project 'web' in environment 'staging' and return the token value once.

### Flag Archive Management

Engineering teams clean up old flags rather than letting code accumulate dead conditionals. The Unleash archive endpoints let an automation list archived flags and either permanently remove them or revive a specific flag if a rollback becomes necessary. POST /api/admin/archive/revive/{featureName} brings an archived flag back without a manual recreation step.

Example prompt: Revive the archived feature flag named 'new-checkout-experiment' and confirm it is no longer in the archive list.

### AI Agent Feature Flag Operations

An AI agent triaging an incident or applying a feature gate decision can mint a scoped Unleash token, update an addon, or revive a flag without UI navigation. Through Jentic the agent searches for the right operation by intent, loads the schema, and executes - Unleash admin keys stay in the encrypted vault rather than leaking into agent context.

Example prompt: List archived flags, revive any whose name matches 'rollback-*', and post a Slack message via the existing addon.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /api/admin/addons | List all addons |
| POST | /api/admin/addons | Create a new addon |
| PUT | /api/admin/addons/{id} | Update an addon |
| POST | /api/admin/api-tokens | Mint a new API token |
| DELETE | /api/admin/archive/{featureName} | Permanently remove an archived flag |
| POST | /api/admin/archive/revive/{featureName} | Revive an archived feature flag |
| GET | /api/admin/insights | Get admin insights |

## Key resources

- **Addons** — Create, retrieve, update, and delete third-party Unleash integrations
- **API Tokens** — List and create scoped Unleash API tokens
- **Archive** — List, delete, or revive archived feature flags
- **Insights** — Read admin insights about flags and integrations

## Why Jentic

- **Setup:** Wiring the getunleash.io Admin API by hand means passing an admin key in the Authorization header, pointing at your own self-hosted feature-flag host, and keeping addon and token operations straight yourself. Through Jentic you install once, import the Admin API from the API Directory, store the admin key once, and your agent calls it.
- **Permission scoping:** The getunleash.io Admin API puts the addon id and feature name in the URL path (/api/admin/addons/{id}, /api/admin/archive/{featureName}), so a rule can pin your agent to one addon or archived flag. You choose the operations it may call, so destructive ones like deleting an archived flag or minting API tokens are not included unless you add them.
- **Credential handling:** Your getunleash.io admin key 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 addon' or 'revive an archived flag', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **LaunchDarkly** — LaunchDarkly is a hosted feature-flag platform with broader experimentation features; Unleash can self-host
- **Split** — Split offers feature flagging and experimentation as a SaaS
- **Slack** — Slack receives Unleash addon notifications when flags change

## FAQ

### Why is there no official OpenAPI spec for Admin API?

Unleash does not publish an OpenAPI specification for this admin surface. Jentic generates and maintains this spec so that AI agents and developers can call the Unleash Admin API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Unleash Admin API use?

The Admin API uses an apiKey scheme: clients send the key in the Authorization header. Through Jentic this admin key is stored encrypted in the vault and the agent receives only a scoped invocation capability, so the raw admin key never enters the agent's context.

### Can I create an Unleash addon programmatically?

Yes. POST /api/admin/addons accepts the addon configuration (provider, parameters, events) and returns the created addon record. PUT /api/admin/addons/{id} updates an existing one in place; DELETE /api/admin/addons/{id} removes it when the integration is retired.

### What are the rate limits for the Unleash Admin API?

The spec does not declare specific limits. Self-hosted Unleash instances inherit limits from the deployment environment; Unleash Pro and Enterprise tiers apply per-account quotas. Implement backoff on 429 responses for any bulk addon or token rotation script.

### How do I revive an archived feature flag through Jentic?

Search Jentic for 'revive an unleash feature flag'. Jentic returns POST /api/admin/archive/revive/{featureName}; load it with the flag name and execute. Confirm the revival by listing the archive again with GET /api/admin/archive.

### Can I mint scoped Unleash API tokens?

Yes. POST /api/admin/api-tokens creates a new token scoped to the project and environment specified in the payload, and GET /api/admin/api-tokens lists existing tokens. The created token value is returned once, so capture it on creation.