Skip to content
Cloud infrastructure/devops

configcat.com

ConfigCat Public Management sandbox and mock API

**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 Writes persist, data moves on a schedule and every change can fire a signed webhook.

Operations
62
Collections
-
Event types
-
Start this simulation
example request
curl https://your-configcat.slurry.io/v1/me \
  -H "Authorization: Bearer slurry_sim_..."

Your simulation gets its own hostname, key and IP allow-list. Built from API version v1.

What gets simulated

Collections, relationships and state machines are worked out from the spec when you start the simulation.

  • State. Creates, updates and deletes persist and show up in later reads.
  • Behaviour. Records move through their states on a schedule you control, and you can fast-forward up to 30 days.
  • Webhooks. Every change emits a signed, retried event.
  • Failure. Per-endpoint errors, latency and chaos rules, on demand.

Operations

First 12 of 62.

  • POST/v1/code-references
  • POST/v1/code-references/delete-reports
  • GET/v1/configs/{configId}
  • PUT/v1/configs/{configId}
  • DELETE/v1/configs/{configId}
  • GET/v1/configs/{configId}/deleted-settings
  • GET/v1/configs/{configId}/environments/{environmentId}
  • GET/v1/configs/{configId}/environments/{environmentId}/values
  • GET/v1/configs/{configId}/settings
  • POST/v1/configs/{configId}/settings
  • GET/v1/environments/{environmentId}
  • PUT/v1/environments/{environmentId}