How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Algolia Monitoring API

Exposes server status, latency, indexing and reachability metrics for a specific application's Algolia infrastructure. More than a status page: an agent can query the health of its own cluster rather than the global service.

This API exposes 14 operations across 11 paths, and defines 15 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://status.algolia.com.

14 operations 11 paths 15 schemas 1 DELETE11 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://status.algolia.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Algolia Monitoring API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Algolia-Application-Id (appId). An API key is passed in the header as X-Algolia-API-Key (apiKey).

  • appId — Your Algolia application ID.
  • apiKey — Your Algolia Monitoring API key.

Paths & Operations 14

Across 11 paths, the API surfaces 14 operations — 1 DELETE, 11 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

monitoring 14
GET
/{path}
Send requests to the Algolia REST API
customGet 2 params → 200400402403404
POST
/{path}
Send requests to the Algolia REST API
customPost 2 params body → 200400402403404
PUT
/{path}
Send requests to the Algolia REST API
customPut 2 params body → 200400402403404
DELETE
/{path}
Send requests to the Algolia REST API
customDelete 2 params → 200400402403404
GET
/1/status
Retrieve status of all clusters
getStatus → 200401
GET
/1/status/{clusters}
Retrieve cluster status
getClusterStatus 1 param → 200401404
GET
/1/incidents
Retrieve all incidents
getIncidents → 200401
GET
/1/incidents/{clusters}
Retrieve cluster incidents
getClusterIncidents 1 param → 200401404
GET
/1/inventory/servers
Retrieve servers
getServers → 200403
GET
/1/latency/{clusters}
Retrieve search latency times
getLatency 1 param → 200400
GET
/1/indexing/{clusters}
Retrieve indexing monitoring latency
getIndexingTime 1 param → 200400
GET
/1/reachability/{clusters}/probes
Test the reachability of clusters
getReachability 1 param → 200400
GET
/1/infrastructure/{metric}/period/{period}
Retrieve metrics
getMetrics 2 params → 200401
GET
/setClientApiKey
Switch the API key used to authenticate requests
setClientApiKey 1 param → 204

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are Server (7 properties), Incident (2 properties), ProbesMetric (2 properties), ErrorBase (1 property). Each schema is shown below with its type and property counts.

Metric
string
Timestamp
integer
Timestamp, measured in milliseconds since the Unix epoch.
Type
string
ServerStatus
string
Time
array
Time measured by a probe.
ProbesMetric
object
2 properties
Incidents
array
Key-value pairs with the cluster names as keys and the list of incidents reported for this cluster as values.
Server
object
7 properties
Incident
object
Incident details.
2 properties
Status
string
Status of the cluster.
InfraProbes
array
Region
string
Region where the cluster is located.
Period
string
ErrorBase
object
Error.
1 property
Probes
object
Probes and their response.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

algolia-monitoring-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Algolia Monitoring API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.