ConfigCat is a feature flag and configuration management service that lets teams turn features on or off and manage configuration settings across products, configs, and environments without redeploying code. The Public Management API provides programmatic access to organizations, products, configs, environments, feature flags (settings), segments, webhooks, and audit logs.
Power end-to-end data operations for your ConfigCat API with Nexla. Our bi-directional ConfigCat connector is purpose-built for ConfigCat, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to ConfigCat or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your ConfigCat workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
The ConfigCat connector authenticates to the ConfigCat Public Management API using HTTP Basic Authentication. Before creating a credential in Nexla, generate a set of Public API credentials from the ConfigCat Dashboard.
Important
The ConfigCat Public Management API is used to manage your ConfigCat configuration—organizations, products, configs, environments, feature flags, and similar resources. It is not intended for evaluating feature flag values in your applications. For flag evaluation, use a ConfigCat SDK or the ConfigCat Proxy instead.
ConfigCat issues a Basic auth username and password pair that is used to authenticate every API request. These credentials are tied to your user account and inherit your permissions across the organizations you belong to.
Click Add New Credentials, enter a descriptive name (for example, "Nexla Integration"), and click Generate.
Copy both the generated Basic auth username and Basic auth password, and store them securely.
danger
ConfigCat does not store your password. Once you close the credential dialog, the password cannot be retrieved again. If it is lost, you must generate a new set of credentials. Keep these values secure, and do not embed them directly in source code or share them.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your ConfigCat Public API Basic auth username in the Username Or API Key field. This value identifies the API credential used to authenticate Nexla with ConfigCat.
Enter your ConfigCat Public API Basic auth password in the Password field. This value is stored securely and is used together with the username to authenticate each request.
Enter the ConfigCat API base URL in the Base URL field. This is the root endpoint that all API calls are made against, and it defaults to https://api.configcat.com/v1.
The default base URL of https://api.configcat.com/v1 is correct for the standard ConfigCat cloud service. Update this value only if you have been directed to use a different endpoint.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the ConfigCat connector tile, then select the credential that will be used to connect to the ConfigCat instance, and click Next; or, create a new ConfigCat credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common ConfigCat endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
In ConfigCat, resources are organized hierarchically: an organization contains products, each product contains configs and environments, and each config contains settings (feature flags). Many of the endpoints below require the ID of a parent resource. These IDs are GUID-style identifiers that can be retrieved using the corresponding list endpoints (for example, run List Products to obtain product IDs, then List Configs to obtain config IDs) or copied from the ConfigCat Dashboard.
List Organizations
This endpoint returns a list of all organizations accessible to the authenticated user. Use it to discover the organizations available to your ConfigCat account and obtain their IDs for use with other endpoints.
This endpoint requires no additional configuration. Select it to retrieve all organizations that your Public API credentials can access.
Organization IDs returned by this endpoint are required by the List Audit Logs endpoint and can help you navigate to the products within each organization.
List Products
This endpoint retrieves a list of all products from ConfigCat. Use it to discover the products in your account and obtain the product IDs needed by config, environment, segment, and webhook endpoints.
This endpoint requires no additional configuration. Select it to retrieve all products accessible to your credentials.
Get Product
This endpoint retrieves a single product by its ID. Use it when you need detailed information about one specific product rather than the full list.
Enter the ID of the product to retrieve in the Product ID field. Product IDs can be obtained from the List Products endpoint or copied from the ConfigCat Dashboard.
List Configs
This endpoint returns a list of all configs in a product. A config is a collection of related feature flags and settings that are managed together.
Enter the ID of the product whose configs to list in the Product ID field. Product IDs can be obtained from the List Products endpoint.
Get Config
This endpoint retrieves the details of a specific config, including its name and description. Use it when you need information about one config rather than the full list within a product.
Enter the ID of the config to retrieve in the Config ID field. Config IDs can be obtained from the List Configs endpoint.
List Environments
This endpoint returns a list of all environments for a product. Environments (for example, Production, Staging, or Test) let you maintain separate feature flag values for different deployment targets.
Enter the ID of the product for which to list environments in the Product ID field. Product IDs can be obtained from the List Products endpoint.
Get Environment
This endpoint retrieves the details of a specific environment by ID, including its name, description, and color.
Enter the ID of the environment to retrieve in the Environment ID field. Environment IDs can be obtained from the List Environments endpoint.
List Flags
This endpoint retrieves a list of all feature flags (settings) in a config, including their metadata such as name, key, and type. Use it to review the flags defined within a config.
Enter the ID of the config whose flags to list in the Config ID field. Config IDs can be obtained from the List Configs endpoint.
In the ConfigCat Public Management API, a feature flag is referred to as a "setting." The IDs returned by this endpoint can be used as the Setting ID in the Get Setting and Get Setting Value endpoints.
Get Setting
This endpoint retrieves the metadata of a single feature flag (setting) by its ID, including its name, key, hint, tags, and type.
Enter the ID of the feature flag setting to retrieve in the Setting ID field. Setting IDs can be obtained from the List Flags endpoint.
Get Setting Values
This endpoint retrieves all flag values for a specific environment in a config. Use it to capture the complete set of feature flag values that apply to a given config and environment combination.
Enter the ID of the config in the Config ID field. Config IDs can be obtained from the List Configs endpoint.
Enter the ID of the environment to retrieve flag values for in the Environment ID field. Environment IDs can be obtained from the List Environments endpoint.
Get Setting Value
This endpoint retrieves the current value and configuration of a single feature flag setting in a specific environment, including targeting rules and rollout percentages.
Enter the ID of the environment containing the setting in the Environment ID field. Environment IDs can be obtained from the List Environments endpoint.
Enter the ID of the feature flag setting to retrieve in the Setting ID field. Setting IDs can be obtained from the List Flags endpoint.
Get SDK Key
This endpoint retrieves the SDK key for a specific environment within a config. SDK keys are used by ConfigCat SDKs to connect applications to a particular config and environment for flag evaluation.
Enter the ID of the config in the Config ID field. Config IDs can be obtained from the List Configs endpoint.
Enter the ID of the environment to get the SDK key for in the Environment ID field. Environment IDs can be obtained from the List Environments endpoint.
List Segments
This endpoint returns the list of targeting segments defined for a product. Segments are reusable groups of users that can be referenced by targeting rules across feature flags.
Enter the ID of the product whose segments to list in the Product ID field. Product IDs can be obtained from the List Products endpoint.
List Webhooks
This endpoint returns the list of webhooks registered for a product. Webhooks notify external systems when feature flag changes occur.
Enter the ID of the product whose webhooks to list in the Product ID field. Product IDs can be obtained from the List Products endpoint.
List Audit Logs
This endpoint returns audit log events for an organization. Audit logs record changes made to ConfigCat resources and are useful for compliance, monitoring, and change-tracking workflows.
Enter the ID of the organization whose audit logs to retrieve in the Organization ID field. Organization IDs can be obtained from the List Organizations endpoint.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
ConfigCat data sources can also be manually configured to ingest data from any valid ConfigCat Public Management API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
ConfigCat read operations use the GET method. Enter the complete endpoint URL including the protocol (https://) and any required path parameters—for example, https://api.configcat.com/v1/products to list products, or https://api.configcat.com/v1/products/{'{productId}'}/configs to list the configs within a product. Many ConfigCat list endpoints (such as List Products, List Configs, and List Environments) return a top-level JSON array, so use a path to data such as $[*] to treat each element as a record; for an endpoint that returns a single object (such as Get Config), use $ to treat the entire response as one record.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new ConfigCat data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the ConfigCat destination, and select the Send to Destination option from the menu. Select the ConfigCat connector from the list of available destination connectors, then select the credential that will be used to connect to the ConfigCat organization, and click Next; or, create a new ConfigCat credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common ConfigCat endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Each template maps the records in your Nexset to a request body that is sent to the ConfigCat API. The path parameters described below (such as Config ID, Environment ID, and Setting ID) identify the resource to act on. These IDs are GUID-style identifiers that can be retrieved using the corresponding ConfigCat list endpoints in a data source flow or copied from the ConfigCat Dashboard.
Create Config
This endpoint creates a new config in a product. The request body contains the details of the config to create, such as its name and description.
Enter the ID of the product to create the config in, in the Product ID field.
Update Config
This endpoint updates the name and description of a specific config. The request body contains the updated config details.
Enter the ID of the config to update in the Config ID field.
Delete Config
This endpoint deletes a specific config and all of its associated data. Use it to permanently remove a config from a product.
Enter the ID of the config to delete in the Config ID field.
Deleting a config also removes all feature flags and values contained within it. This action cannot be undone, so verify the Config ID before activating the destination.
Create Environment
This endpoint creates a new environment in a product. The request body contains the environment details, such as its name, description, and color.
Enter the ID of the product to create the environment in, in the Product ID field.
Update Environment
This endpoint updates the name, description, or color of an existing environment. The request body contains the updated environment details.
Enter the ID of the environment to update in the Environment ID field.
Delete Environment
This endpoint deletes an environment from a product. Use it to permanently remove an environment and its associated flag values.
Enter the ID of the environment to delete in the Environment ID field.
Create Flag
This endpoint creates a new feature flag (setting) in a specific config. The request body contains the flag definition, including its name, key, type, and hint.
Enter the ID of the config to create the flag in, in the Config ID field.
Update Flag
This endpoint updates the metadata (name, hint, key, and tags) of a feature flag (setting). The request body contains the updated metadata.
Enter the ID of the feature flag setting to update in the Setting ID field.
This endpoint updates flag metadata only. To change the value of a flag in a specific environment, use the Update Setting Value or Replace Setting Value endpoints.
Delete Flag
This endpoint deletes a feature flag (setting) by its ID. Use it to permanently remove a flag and its values from all environments in the config.
Enter the ID of the feature flag setting to delete in the Setting ID field.
Update Setting Value
This endpoint partially updates a feature flag setting value using JSON Patch operations. Use it to make targeted changes—such as updating a single targeting rule or the default value—without replacing the entire setting configuration.
Enter the ID of the environment containing the setting in the Environment ID field.
Enter the ID of the feature flag setting to update in the Setting ID field.
The request body for this endpoint must be formatted as a JSON Patch document describing the operations to apply. For complete details, see the ConfigCat Public Management API documentation.
Replace Setting Value
This endpoint replaces the entire configuration of a feature flag setting in an environment, including its value, targeting rules, and rollout percentages. Use it when you want to fully overwrite a setting's configuration rather than apply incremental changes.
Enter the ID of the environment containing the setting in the Environment ID field.
Enter the ID of the feature flag setting to replace in the Setting ID field.
Replace All Setting Values
This endpoint bulk-replaces every feature flag value in a single config and environment in one atomic call. Use it to apply a complete set of flag values to a config/environment combination at once.
Enter the ID of the config containing the settings in the Config ID field.
Enter the ID of the environment whose values to replace in the Environment ID field.
Create Segment
This endpoint creates a new targeting segment in a product. Segments are reusable user groups that can be referenced by targeting rules across feature flags. The request body contains the segment definition.
Enter the ID of the product to create the segment in, in the Product ID field.
Create Webhook
This endpoint creates a webhook bound to a specific config and environment. Webhooks notify external systems when feature flag changes occur. The request body contains the webhook configuration, such as the target URL and HTTP method.
Enter the ID of the config the webhook is bound to in the Config ID field.
Enter the ID of the environment the webhook is bound to in the Environment ID field.
Delete Webhook
This endpoint deletes a webhook by its ID. Use it to permanently remove a registered webhook from a product.
Enter the ID of the webhook to delete in the Webhook ID field. Webhook IDs can be obtained from the List Webhooks endpoint in a data source flow.
ConfigCat destinations can also be manually configured to send data to any valid ConfigCat Public Management API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
ConfigCat write operations use POST (create), PUT (replace), PATCH (partial update, including JSON Patch operations against setting values), and DELETE. ConfigCat expects JSON request bodies for all of these operations. For update, replace, and delete operations, include the ID of the object to be modified at the end of the URL—for example, https://api.configcat.com/v1/configs/{'{configId}'} to update a config, or https://api.configcat.com/v1/settings/{'{settingId}'} to update a flag. Nexla can also automatically send the response received from the ConfigCat API after each call to a new Nexla webhook data source.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To begin sending data to ConfigCat, open the destination resource menu, and select Activate.
The Nexset data will not be sent to ConfigCat until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
