# Webhook Overview

{% 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 section to register webhook endpoints and consume event notifications.

### Overview

Webhooks will automatically notify you on airline changes that affect your customers’ bookings. For example, when an airline has changed the flight schedule affecting one of your orders, the Atlas API will send a notification about this event to your server, and you can process it. For example, you may take actions by updating your database or emailing the customer.

> Atlas provides the webhook functionality on the “best possible basis”. Atlas does not take the responsibility for providing all the notifications. For any schedule changes please always refer to the email sent by the airline to the email id provided in the booking request.

### Typical flow

{% stepper %}
{% step %}

### Register your endpoint

Use [Webhook Registration & Incidents](/api-document/api-reference/webhook-and-incident-apis/webhook-registration-and-incidents.md) to save the webhook URL before go-live.
{% endstep %}

{% step %}

### Receive and process events

Handle ticketing, schedule, airline, email, and incident notifications. Currently, we send out webhook notifications in four scenarios:

1. Ticket booked: [Ticketing Complete Notification](/api-document/readme/webhook-overview/ticketing-complete-notification.md)
2. Change in flight schedule: [Schedule Change Notification](/api-document/readme/webhook-overview/schedule-change-notification.md)
3. Airline status update: [Airline Status Update Notification](/api-document/readme/webhook-overview/airline-status-update-notification.md)
4. Email received: [Email Notification](/api-document/readme/webhook-overview/email-notification.md)
   {% endstep %}

{% step %}

### Reconcile when needed

Use incident queries and order APIs to confirm final state.

1. Incident notification: [Incident Notification](/api-document/readme/webhook-overview/incident-notification.md)
2. Incident query: [Incident Query](/api-document/readme/webhook-overview/incident-query.md)
   {% endstep %}
   {% endstepper %}


---

# Agent Instructions: 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:

```
GET https://resources.atriptech.com/api-document/readme/webhook-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.