Skip to content

Commit bdb134a

Browse files
fix(cts): create multifeed composition example (generated)
algolia/api-clients-automation#6058 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Gavin Wade <gavin.wade12@gmail.com>
1 parent b7f1041 commit bdb134a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

algoliasearch/Clients/MonitoringConfiguration.cs

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
/*
22
* Algolia Monitoring API
33
*
4-
* ## Base URLs Base URL for the Monitoring API: - `https://status.algolia.com` **All requests must use HTTPS.** ## Availability and authentication Access to the Infrastructure endpoints is available as part of the [Premium or Elevate plans](https://www.algolia.com/pricing). To authenticate requests to the Infrastructure endpoints, add these headers: - `x-algolia-application-id`. Your Algolia application ID. - `x-algolia-api-key`. Your Monitoring API key. You can find your application ID and API key in the [Algolia dashboard](https://dashboard.algolia.com/account/api-keys). Other endpoints don't require authentication. ## Response status and errors The Monitoring API returns JSON responses. Since JSON doesn't guarantee any specific ordering, don't rely on the order of attributes in the API response. Successful responses return `2xx` statuses. Client errors return `4xx` statuses. Server errors return `5xx` statuses. Error responses have a `message` property with more information. ## Version The current version of the Monitoring API is version 1, indicated by the `/1/` in each endpoint's URL.
4+
* The metrics exposed by this API are based on results from external monitoring probes checking Algolia’s infrastructure. These metrics **reflect the overall infrastructure status and don’t represent the performance of the specific APPID** used for authentication. ## Base URLs Base URL for the Monitoring API: - `https://status.algolia.com` **All requests must use HTTPS.** ## Availability and authentication Access to the Infrastructure endpoints is available as part of the [Premium or Elevate plans](https://www.algolia.com/pricing). To authenticate requests to the Infrastructure endpoints, add these headers: - `x-algolia-application-id`. Your Algolia application ID. - `x-algolia-api-key`. Your Monitoring API key. You can find your application ID and API key in the [Algolia dashboard](https://dashboard.algolia.com/account/api-keys). Other endpoints don't require authentication. ## Response status and errors The Monitoring API returns JSON responses. Since JSON doesn't guarantee any specific ordering, don't rely on the order of attributes in the API response. Successful responses return `2xx` statuses. Client errors return `4xx` statuses. Server errors return `5xx` statuses. Error responses have a `message` property with more information. ## Version The current version of the Monitoring API is version 1, indicated by the `/1/` in each endpoint's URL.
55
*
66
* The version of the OpenAPI document: 1.0.0
77
* Generated by: https://github.com/openapitools/openapi-generator.git

0 commit comments

Comments
 (0)