ConfigCat Public Management API

Name: ConfigCat Public Management API API
Brand: ConfigCat Public Management API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsCi Cdbasic91 EndpointsREST

For Agents

Manage ConfigCat feature flags, configs, environments, segments, and team permissions programmatically. Useful for agents that automate flag rollouts, audit reviews, and SDK key rotation.

Quickstart

Get started with ConfigCat Public Management API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"update a configcat feature flag value"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with ConfigCat Public Management API API.

Create and update feature flags inside a config and target them to specific environments

Roll out percentage-based or segment-based releases by updating flag values per environment

Provision new environments and configs under a product for staged deployments

Review audit logs at the product or organization level to track who changed which flag

GET STARTED

Start building with ConfigCat Public Management API API

Explore with Jentic

View OpenAPI Document

Use for: I want to create a new boolean feature flag in ConfigCat for a beta rollout, Update the value of a feature flag in the production environment, List all feature flags inside a specific config, Retrieve the SDK key for an environment so my deployment pipeline can use it

Not supported: Does not handle runtime flag evaluation, A/B test analytics, or end-user delivery — use for ConfigCat platform management only.

The ConfigCat Public Management API lets developers and AI agents administer feature flags, configs, environments, products, and segments in the ConfigCat platform programmatically. It exposes 91 REST endpoints across 20 resource groups including Feature Flags & Settings, Configs, Environments, Segments, Webhooks, Permission Groups, Audit Logs, and Code References. The API is for management workflows such as creating flags, rolling out targeted releases, and reviewing audit history; flag value evaluation at runtime should still be done with the ConfigCat SDKs or Proxy.

Use Cases

Patterns agents use ConfigCat Public Management API API for, with concrete tasks.

★ Automate Feature Flag Rollouts in CI/CD

Use the ConfigCat Public Management API to flip flags as part of a deployment pipeline. After a build is promoted to staging, the pipeline calls PATCH /v1/settings/{settingId}/value to enable the flag in the staging environment, runs smoke tests, then promotes the same change to production. This keeps flag state in lock-step with deploy state and removes the manual dashboard click. Setup with Jentic takes under an hour versus a few hours integrating directly.

Call PATCH /v1/settings/{settingId}/value to set the new-checkout flag to true in the production environment, then read it back with GET to confirm the change.

Compliance Audit Review

Pull audit log entries for a product or organization to satisfy SOC 2 or ISO 27001 evidence requests. The API exposes GET /v1/products/{productId}/auditlogs and GET /v1/organizations/{organizationId}/auditlogs with date range filters, so an agent can collect every flag change in the audit window and export it as CSV. The work that took hours of dashboard clicks finishes in seconds.

Fetch all audit log entries for product 12345 between 2026-01-01 and 2026-03-31 via GET /v1/products/{productId}/auditlogs and write the result to audit-q1.csv.

Programmatic Segment Targeting

Create and update user segments to target rollouts at cohorts such as internal staff, beta testers, or a single tenant. The agent calls POST /v1/products/{productId}/segments to define the segment with comparator rules (email contains, country equals), then references that segment from a flag's targeting rules. This is well suited for support engineers who need to enable a fix for one customer while a wider release is paused.

Create a segment named internal-staff that matches users where email ends with @example.com, then attach it as a targeting rule on the new-dashboard flag.

AI Agent Flag Operations via Jentic

Expose ConfigCat management as a tool an AI agent can call from inside a chat or workflow. The agent searches Jentic for configcat manage feature flag, loads the matching operation schema, and executes it with credentials kept server-side in the Jentic vault. The agent never sees the raw Basic auth password, and the same wrapper works whether the underlying call is creating a flag, listing configs, or rotating an SDK key.

Through Jentic, search for manage configcat feature flag, load the PATCH /v1/settings/{settingId}/value operation, and execute it to disable the legacy-checkout flag in production.

Key Endpoints

91 endpoints — the configcat public management api lets developers and ai agents administer feature flags, configs, environments, products, and segments in the configcat platform programmatically.

METHOD

PATH

DESCRIPTION

GET

/v1/configs/{configId}/settings

List feature flags in a config

POST

/v1/configs/{configId}/settings

Create a new feature flag

PATCH

/v1/settings/{settingId}/value

Update a flag value in an environment

GET

/v1/products/{productId}/auditlogs

List audit log entries for a product

POST

/v1/products/{productId}/segments

Create a user segment for targeting

GET

/v1/configs/{configId}/environments/{environmentId}

Retrieve the SDK key for an environment

POST

/v1/products/{productId}/webhooks

Create a webhook that fires on flag changes

GET

/v1/configs/{configId}/settings

List feature flags in a config

POST

/v1/configs/{configId}/settings

Create a new feature flag

PATCH

/v1/settings/{settingId}/value

Update a flag value in an environment

GET

/v1/products/{productId}/auditlogs

List audit log entries for a product

POST

/v1/products/{productId}/segments

Create a user segment for targeting

Why though Jentic?

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

Credential isolation

ConfigCat Basic auth credentials are stored encrypted in the Jentic vault. Agents call operations through scoped Jentic tokens; the raw username and password never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (for example, update configcat feature flag value) and Jentic returns the matching ConfigCat operation with its input schema, so the agent can call the right endpoint without browsing the docs.

Time to first call

Direct ConfigCat integration: 2-4 hours for auth, error handling, and per-environment routing. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

LaunchDarkly API

LaunchDarkly is a larger feature flag platform with deeper experimentation features

Choose LaunchDarkly when the team already has experimentation, audit, and approval workflows that integrate with it; choose ConfigCat for a smaller, lower-cost flag service with a simpler API surface.

Alternative

Split API

Split focuses on feature delivery plus statistical experimentation

Pick Split when the use case is A/B testing tied to product metrics; pick ConfigCat for straightforward flag and config management.

Alternative

Unleash API

Unleash is an open-source feature flag service with a self-hosted option

Pick Unleash when self-hosting is a hard requirement; pick ConfigCat for a hosted, lower-ops option.

Complementary

Statsig API

Statsig pairs flag management with product analytics and experiment readouts

Use Statsig alongside ConfigCat when you want experiment analytics layered on top of basic flag operations.

FAQs

Specific to using ConfigCat Public Management API API through Jentic.

What authentication does the ConfigCat Public Management API use?

It uses HTTP Basic authentication with Public API credentials issued from the ConfigCat dashboard. When you call it through Jentic, the credentials live in the Jentic vault and never enter the agent's prompt or context.

Can I evaluate feature flag values for end users with this API?

No. The Public Management API is for management actions only — creating, listing, updating, and deleting flags and configs. For runtime evaluation of flag values for your end users you should use the ConfigCat SDKs or the ConfigCat Proxy, which are designed for low-latency reads.

What are the rate limits for the ConfigCat Public Management API?

Rate-limited calls return X-Rate-Limit-Remaining and X-Rate-Limit-Reset headers describing the current window. When the limit is exceeded the API responds with HTTP 429 and a Retry-After header, so an agent can back off and retry after the indicated interval.

How do I update a feature flag value through Jentic?

Run pip install jentic, then use the async pattern: await client.search('update configcat feature flag value'), load the matching operation schema, and execute it. The underlying call is PATCH /v1/settings/{settingId}/value scoped to a specific environment.

Can I retrieve the SDK key for an environment via the API?

Yes. Call GET /v1/configs/{configId}/environments/{environmentId} to retrieve the SDK key for a specific environment, which is useful for rotating keys from a deployment pipeline or rotating after an offboarding event.

Does the API support webhooks for flag changes?

Yes. Use POST /v1/products/{productId}/webhooks to create a webhook scoped to a product, then GET /v1/products/{productId}/webhooks to list configured webhooks. ConfigCat will POST to your endpoint when a flag in that product changes.