> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/api-document/readme/webhook-overview/airline-status-update-notification.md).

# Airline Status Update Notification

{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva on ATRIP for instant diagnostics.

<a href="https://www.atriptech.com/" class="button primary" data-icon="comments">Ask Eva</a>
{% endhint %}

Use this webhook when you need to react to airline-level availability changes.

### Trigger

Atlas sends `airline.status` when an airline moves between active, maintenance, or inactive states.

### What you should do

When you receive this event:

* update internal airline availability flags
* adjust search caching or routing behavior
* suppress booking flows for inactive or maintenance airlines if needed

### Endpoint

POST to the webhook URL you registered with Atlas.

### Fields to read first

* `type`
* `data.airline`
* `data.airlineStatus`

### Airline status values

* `Active`
* `Maintenance`
* `Inactive`

### Typical payload

```json
{
  "data": {
    "airline": ["TO", "HV"],
    "airlineStatus": "Active"
  },
  "status": -1,
  "type": "airline.status"
}
```

### Notes

* `status` is internal and should not be used for business logic
* this event is operational, not order-specific
* treat `Maintenance` and `Inactive` as non-bookable until recovery

{% tabs %}
{% tab title="Schema" %}
**data**

* **Type:** Object
* **Required:** Yes
* **Description:** Contains airline information including the airline codes and their status.
* **Default:** None
* **Example:**

  ```json
  {
    "airline": ["TO", "HV"],
    "airlineStatus": "Active"
  }
  ```

**data.airline**

* **Type:** Array of Strings
* **Required:** Yes
* **Description:** List of airline codes associated with the response.
* **Default:** None
* **Example:** `["TO", "HV"]`

**data.airlineStatus**

* **Type:** String
* **Required:** Yes
* **Description:** Indicates the operational status of the airline(s).
* **Valid values:**
  * Active = Online
  * Maintenance = Airline is under maintenance
  * Inactive = Offline
* **Default:** None
* **Example:** `"Active"`

**status**

* **Type:** Integer
* **Required:** Yes
* **Description:** Indicates the response status. Only for internal use by Atlas.
* **Default:** None
* **Example:** `-1`

**type**

* **Type:** String
* **Required:** Yes
* **Description:** Specifies the type of response message.
* **Valid value:**
  * airline.status
* **Default:** None
* **Example:** `"airline.status"`
  {% endtab %}

{% tab title="Samples" %}

```json
{
  "data":{
     "airline":["TO","HV"],
     "airlineStatus":"Active"},
  "status":-1,
  "type":"airline.status"
}
```

{% endtab %}
{% endtabs %}

### Related pages

* [Webhook Overview](/api-document/readme/webhook-overview.md)
* [Search Errors](/api-document/troubleshooting-and-support/errors-handing/search-errors.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://resources.atriptech.com/api-document/readme/webhook-overview/airline-status-update-notification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.