Webhooks are generally used to connect two separate applications. They are automated messages that can be sent whenever a certain scenario occurs e.g. when an Arlo contact record, or an order is created or updated.
Information about the scenario is automatically sent to another application such as an external marketing system (e.g. Mailchimp), or an accounting tool (e.g. QuickBooks), usually using a tool like Zapier (Zaps need to be created to connect applications) or Tray.io.
When the subscribed scenario happens in Arlo, it generates data about it and sends it to the webhook URL of the second application - the one you want to do something based on the scenario from Arlo.
The action application can then send a callback message, often with an HTTP status code to let the trigger application know if the data was received successfully or not and you can see this in Arlo.
- Support for filtering of events per endpoint (i.e. you can nominate what you're interested in and what you aren't).
- Support JSON and XML format in callbacks.
- Support retrieving details of all events in a single batch API call. For example, if a webhook call includes details of 20 events, you can use a single API call to fetch the details of all 20 updated resources at once, rather than 20 separate calls.
- Hook callbacks are executed within 4 seconds.
Arlo does not currently offer out-of-the-box integrations using Arlo's Webhooks. You will need to set these up separately.
- Open the Settings menu item.
- From the Advanced section, select Webhook endpoints.
- Select New.
- Enter the relevant details and then press Save.
For more information regarding Webhook please see the developer documentation. You can also learn more general information about Webhooks here.