Automate ConfigCat Public Management
HumDay reads ConfigCat Public Management’s own published API description and derives 62 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What ConfigCat Public Management is
**Base API URL**: https://api.configcat.com If you prefer the swagger documentation, you can find it here: [Swagger UI](https://api.configcat.com/swagger). The purpose of this API is to access the ConfigCat platform programmatically. You can **Create**, **Read**, **Update** and **Delete** any entities like **Feature Flags, Configs, Environments** or **Products** within ConfigCat. The API is based
API host: api.configcat.com
What HumDay can do in ConfigCat Public Management
35 documented operations change something in ConfigCat Public Management.
- POSTCreate Tag
/v1/products/{productId}/tags - POSTCreate Flag
/v1/configs/{configId}/settings - POSTCreate Config
/v1/products/{productId}/configs - POSTCreate Segment
/v1/products/{productId}/segments - POSTCreate Environment
/v1/products/{productId}/environments - POSTCreate Product
/v1/organizations/{organizationId}/products - DELETEDelete Tag
/v1/tags/{tagId} - PUTUpdate Tag
/v1/tags/{tagId} - POSTInvite Member
/v1/products/{productId}/members/invite - DELETEDelete Config
/v1/configs/{configId} - PUTUpdate Config
/v1/configs/{configId} - DELETEDelete Product
/v1/products/{productId} - PUTUpdate Product
/v1/products/{productId} - DELETEDelete Segment
/v1/segments/{segmentId} - PUTUpdate Segment
/v1/segments/{segmentId} - DELETEDelete Flag
/v1/settings/{settingId} - PATCHUpdate Flag
/v1/settings/{settingId} - DELETEDelete Environment
/v1/environments/{environmentId} - PUTUpdate Environment
/v1/environments/{environmentId} - PATCHUpdate value
/v1/settings/{settingKeyOrId}/value - PUTReplace value
/v1/settings/{settingKeyOrId}/value - DELETEDelete Member from Product
/v1/products/{productId}/members/{userId} - DELETEDelete Member from Organization
/v1/organizations/{organizationId}/members/{userId} - POSTUpdate Member Permissions
/v1/organizations/{organizationId}/members/{userId} - PATCHUpdate value
/v1/environments/{environmentId}/settings/{settingId}/value - PUTReplace value
/v1/environments/{environmentId}/settings/{settingId}/value - POSTAdd or update Integration link
/v1/environments/{environmentId}/settings/{settingId}/integrationLinks/{integrationLinkType}/{key} - POSTUpdate code references
/v1/code-references - POSTUpdate Connect
/v1/jira/Connect - POSTUpdate delete reports
/v1/code-references/delete-reports - POSTCreate Permission Group
/v1/products/{productId}/permissions - DELETEDelete Integration link
/v1/environments/{environmentId}/settings/{settingId}/integrationLinks/{integrationLinkType}/{key} - DELETEDelete Permission Group
/v1/permissions/{permissionGroupId} - PUTUpdate Permission Group
/v1/permissions/{permissionGroupId} - POSTUpdate key
/v1/jira/environments/{environmentId}/settings/{settingId}/integrationLinks/{key}
What HumDay can read from ConfigCat Public Management
These are the operations a schedule or a trigger can watch.
- GETGet authenticated user details
/v1/me - GETList Products
/v1/products - GETList Organizations
/v1/organizations - GETList Settings by Tag
/v1/tags/{tagId}/settings - GETList Tags
/v1/products/{productId}/tags - GETList Flags
/v1/configs/{configId}/settings - GETList Configs
/v1/products/{productId}/configs - GETList Product Members
/v1/products/{productId}/members - GETList Segments
/v1/products/{productId}/segments - GETList Environments
/v1/products/{productId}/environments - GETList Organization Members
/v1/organizations/{organizationId}/members - GETGet Tag
/v1/tags/{tagId} - GETGet Config
/v1/configs/{configId} - GETGet Product
/v1/products/{productId} - GETGet Segment
/v1/segments/{segmentId} - GETGet Flag
/v1/settings/{settingId} - GETGet Environment
/v1/environments/{environmentId} - GETGet value
/v1/settings/{settingKeyOrId}/value - GETGet SDK Key
/v1/configs/{configId}/environments/{environmentId} - GETGet Integration link
/v1/integrationLink/{integrationLinkType}/{key}/details - GETGet values
/v1/configs/{configId}/environments/{environmentId}/values - GETGet value
/v1/environments/{environmentId}/settings/{settingId}/value - GETList Audit log items for Product
/v1/products/{productId}/auditlogs - GETList Audit log items for Organization
/v1/organizations/{organizationId}/auditlogs - GETList Permission Groups
/v1/products/{productId}/permissions - GETList Deleted Settings
/v1/configs/{configId}/deleted-settings - GETGet Permission Group
/v1/permissions/{permissionGroupId}
How automating ConfigCat Public Management works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live ConfigCat Public Management account.
- Grant access, then go live. You approve the specific ConfigCat Public Management operations it may use — and only those.
Popular ConfigCat Public Management integrations
Connect ConfigCat Public Management to the tools people pair it with most.
- ConfigCat Public Management and OData for namespace microsoft.graphintegration
- ConfigCat Public Management and Cloudflareintegration
- ConfigCat Public Management and NetBoxintegration
- ConfigCat Public Management and GitHubintegration
- ConfigCat Public Management and Mistintegration
- ConfigCat Public Management and Loket.nlintegration
- ConfigCat Public Management and Atlassian The Jira Cloud platformintegration
- ConfigCat Public Management and Magento B2Bintegration
- ConfigCat Public Management and Stripeintegration
- ConfigCat Public Management and Zuora Reference Billingintegration
- ConfigCat Public Management and bunqintegration
- ConfigCat Public Management and DocuSignintegration
Automate ConfigCat Public Management with these
- OData for namespace microsoft.graph11412 operations
- GitHub811 operations
- Atlassian The Jira Cloud platform474 operations
- Gitlab358 operations
- JIRA 7.6.1324 operations
- Appcenter App Center Client323 operations
- Gitea .321 operations
- Bitbucket292 operations
- Keycloak Admin281 operations
- Apple App Store Connect251 operations
- Files.com222 operations
- Vmware vRealize Network Insight Reference161 operations
Categories
Questions about ConfigCat Public Management automation
- Can HumDay connect to ConfigCat Public Management?
- Yes. HumDay reads ConfigCat Public Management's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 62 operations are documented.
- Do I need to write code to automate ConfigCat Public Management?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your ConfigCat Public Management account.
- What can HumDay do in ConfigCat Public Management?
- 35 of the 62 documented operations change something in ConfigCat Public Management, and 27 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my ConfigCat Public Management account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to ConfigCat Public Management is held behind that approval.
Where this came from
The operations above are read from a published API description for ConfigCat Public Management at api.configcat.com/docs/v1/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.