Mock sample for your project: ConfigCat Public Management API
Integrate with "ConfigCat Public Management API" from configcat.com in no time with Mockoon's ready to use mock sample
ConfigCat Public Management API
Version: v1
Integrate third-party APIs faster by using "ConfigCat Public Management API" ready-to-use mock sample. Mocking this API will help you accelerate your development lifecycles and improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
It also helps reduce your dependency on third-party APIs: no more accounts to create, API keys to provision, accesses to configure, unplanned downtime, etc.
Description
Base API URL: https://api.configcat.com
If you prefer the swagger documentation, you can find it here: Swagger UI.
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 on HTTP REST, uses resource-oriented URLs, status codes and supports JSON
and JSON+HAL format. Do not use this API for accessing and evaluating feature flag values. Use the SDKs instead.
OpenAPI Specification
The complete specification is publicly available here: swagger.json.
You can use it to generate client libraries in various languages with OpenAPI Generator or
Swagger Codegen to interact with this API.
Authentication
This API uses the Basic HTTP Authentication Scheme.
Throttling and rate limits
All the rate limited API calls are returning information about the current rate limit period in the following HTTP headers:
| Header | Description |
| :- | :- |
| X-Rate-Limit-Remaining | The maximum number of requests remaining in the current rate limit period. |
| X-Rate-Limit-Reset | The time when the current rate limit period resets. |
When the rate limit is exceeded by a request, the API returns with a HTTP 429 - Too many requests status along with a Retry-After HTTP header.
Other APIs in the same category
Airbyte Configuration API
https://airbyte.io.
This API is a collection of HTTP RPC-style methods. While it is not a REST API, those familiar with REST should find the conventions of this API recognizable.
Here are some conventions that this API follows:
All endpoints are http POST methods.
All endpoints accept data via application/json request bodies. The API does not accept any data via query params.
The naming convention for endpoints is: localhost:8000/{VERSION}/{METHODFAMILY}/{METHODNAME} e.g. localhost:8000/v1/connections/create.
For all update methods, the whole object must be passed in, even the fields that did not change.
Change Management:
The major version of the API endpoint can be determined / specified in the URL localhost:8080/v1/connections/create
Minor version bumps will be invisible to the end user. The user cannot specify minor versions in requests.
All backwards incompatible changes will happen in major version bumps. We will not make backwards incompatible changes in minor version bumps. Examples of non-breaking changes (includes but not limited to...):
Adding fields to request or response bodies.
Adding new HTTP endpoints.
StackExchange
Patchman-engine API
Syntax of the filtername] query parameters is described in [Filters documentation
Swagger Generator
AutoSuggest Client
Interzoid Get Full Name Match Similarity Key API
VictorOps
to a total number of API calls per month. Also, some of these API calls have rate limits.
NOTE: In this documentation when creating a sample curl request (clicking the TRY IT OUT! button), in some API
viewing interfaces, the '@' in an email address may be encoded. Please note that the REST endpoints will not
process the encoded version. Make sure that the encoded character '%40' is changed to its unencoded form before
submitting the curl request.
