# About Status API

**Learn how the Status API helps you monitor the operational health of Demand API endpoints and automate responses to service degradation.**

## Overview

The Status API provides the real-time operational status of monitored Demand API endpoint groups and individual endpoints.

* Use the Status API to detect service degradation and automatically adapt your integration.
* For example, you can temporarily disable affected functionality, retry requests with backoff, or fail over to alternative workflows while an incident is in progress.


Unlike relying on failed requests to detect service issues, the Status API lets your application check the operational status of Demand API endpoints before sending requests.

## Benefits

Integrating with the Status API enables you to:

✓ Detect service degradation before it significantly impacts your users.
✓ Reduce the mean time to detect (MTTD) operational incidents.
✓ Automatically enable failover or degraded operating modes.
✓ Avoid unnecessary retries against endpoints experiencing outages.
✓ Monitor the health of related endpoint groups instead of checking individual endpoints when appropriate.

## How it works

The Status API continuously evaluates the health of selected Demand API endpoints.

When you call the Status API, it returns the current operational status for:

* Endpoint groups, such as **Reservations** or **Rates and availability.**
* The individual endpoints within each group.


Each status is one of three values:

| Status | Meaning |
|  --- | --- |
| **up** | The endpoint is operating normally. |
| **minor_outage** | The endpoint is reachable but experiencing degradation, such as elevated latency or partial errors. |
| **major_outage** | The endpoint is experiencing a significant outage and requests are likely to fail. |


If an endpoint or group is degraded, the response also includes:

* When the issue began (`since`)
* A human-readable reason describing the incident.


## Endpoint groups

The Status API reports the health of monitored endpoints grouped by functional area.

Currently only available for accommodations.

Currently, the following groups are monitored for the indicated stable Demand API versions.

| Group | Endpoint | API versions |
|  --- | --- | --- |
| **Rates and availability** | /accommodations/search | 3.1 3.2 |
|  | /accommodations/availability | 3.1 3.2 |
|  | /accommodations/bulk-availability | 3.1 |
| **Reservations** | /orders/preview | 3.1 3.2 |
|  | /orders/create | 3.1 3.2 |
|  | /orders/details | 3.1 3.2 |
|  | /orders/details/accommodations | 3.1 3.2 |
|  | /orders/cancel | 3.1 3.2 |
|  | /orders/modify | 3.1 3.2 |


The status reported for a group always reflects the most severe status of any endpoint within that group.

For example, if one endpoint has a `major_outage`, the group status will also be `major_outage`, even if the remaining endpoints are operational.

Current state only
The Status API reports the current operational state only.
It does **not provide** historical availability data, incident history, or uptime statistics.

## Next steps

To start monitoring the operational status of Demand API endpoints, see:

* The [Integration guide](/demand/docs/additional-services/status-api/integration-guide) for technical details.
* The [Status API specifications](/demand/docs/additional-services/status-api/status-api-open-specs) for schema and examples.