> For the complete documentation index, see [llms.txt](https://docs.remote.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.remote.it/developer-tools/webhooks.md).

# Webhooks

Receive HTTP push notifications when your devices go online or offline, and build integrations on top of Remote.It webhooks.

remote.it supports **webhooks** which allow you to receive HTTP push notifications for device online/offline notifications. This allows you to build integrations on top of remote.it. Some examples are to perform debug operations on devices which go offline, send messages, or check for the device IP change when it comes online.

Your webhook consumer is a simple HTTP endpoint. It is not an email address or a general website url. It must satisfy the following conditions:

* It's available in a publicly accessible HTTPS, non-localhost URL
* It will respond to the remote.it Webhook push (HTTP POST request) with a `HTTP 200` ("OK") response within 5 seconds

If a delivery fails (i.e. server unavailable or responded with a non-200 HTTP status code), the push might subsequently be retried a couple of times. If the webhook URL continues to be unresponsive the webhook might be disabled by remote.it, and must be re-enabled again manually.

For additional information on Webhooks, you can use any of these resources:

* [RequestBin: Webhooks – The Definitive Guide](https://requestbin.com/blog/working-with-webhooks/)
* [requestbin.com](https://requestbin.com/) is a great tool for testing webhooks
* [GitHub Developer Guide: Webhooks](https://developer.github.com/webhooks/)

## Enabling a Webhook

You can add a webhook endpoint to your account, by signing in to your account and navigating to the account page. Select the types of notifications you to which you wish to subscribe and enter the webhook url.

{% hint style="info" %}
A webhook url is not a email address or a general website url. If you wish to receive email notifications select the email checkbox. It is also a VARCHAR 255 field.
{% endhint %}

<figure><img src="https://413684331-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LUSyCxfB8Qr7Kz5eeQu%2Fuploads%2FofV4UjQgcPspmtxiqIJ6%2FRemote_It_-_Settings_-_notifications.png?alt=media&amp;token=2d5ae49d-2f23-42c4-9b3e-6c743c871b32" alt="Account notification settings with webhook URL field and subscription checkboxes"><figcaption></figcaption></figure>

## Whats in the Webhook?

The body of a webhook call contains the latest state information of the device or service. This can be recorded in a database to review later. You will receive unique webhook notifications for the device and each service registered to that device when their state changes.

| Value   | Description                                               |
| ------- | --------------------------------------------------------- |
| Address | Public IP Address of the device/service                   |
| Device  | Unique ID of the device or service                        |
| Email   | Email address of the owner of the device                  |
| Name    | Name of the device or service                             |
| State   | {online/offline} state being recorded                     |
| Time    | When the state change happened in UTC time string format. |
| Type    | Type of state change that happened                        |

## Notification Latency

* Online notifications will be sent almost immediately.
* Offline notifications will be sent almost immediately, if the system was shutdown or rebooted using specific "shutdown" or "reboot" commands. Using command line options to stop and start the connectd daemons directly will also send notifications immediately.
* If the reason for your device going offline is an unexpected interruption of power or internet connection, it may take up to 15 minutes to receive the offline notification.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.remote.it/developer-tools/webhooks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
