# API Events API Events allow you to receive near-real-time notifications about key activities in the Mews system. These notifications are delivered via Webhooks or WebSockets, offering flexible solutions for various use cases. For an overview and guidance on selecting the best method for your needs, see [Ways to communicate](/connector-api/events/communicate.md). To start using API Events, configure your system to receive event notifications and [Contact support](/connector-api/contact-support.md) to register your Webhook or WebSocket. ## Webhooks Mews currently supports two types of Webhook: **General Webhooks** and **Integration Webhooks**. Both types of Webhook message are sent as `HTTP POST` requests with the event details in the JSON body, just like standard requests to API endpoints. For guidance on setting up a Webhooks server, registering the URL, and responding to Webhook messages, see our [Webhooks FAQ](/connector-api/events/wh-faq.md). ## Contents * [Ways to communicate](/connector-api/events/communicate.md) – an explanation of API Operations, Webhooks and WebSockets * [General Webhooks](/connector-api/events/wh-general.md) – a single Webhook that consolidates multiple event types * [Integration Webhooks](/connector-api/events/wh-integration.md) – individual Webhooks focused on integration state changes * [Webhooks FAQ](/connector-api/events/wh-faq.md) – answers to common questions about Webhooks * [WebSockets](/connector-api/events/websockets.md) – an alternative form of API Event for special use cases --- # 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://docs.mews.com/connector-api/events.md?ask= ``` 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.