# Webhooks

If your integration needs to execute actions in response to something happening within the ev.energy system, you can use webhooks to receive notifications of those events rather than having to constantly poll for changes.

To find out about the events we currently support, click [here](https://www.svix.com/event-types/eu/org_2eoqqPZwMlztxZbIXr0eeqYTscI/).

All webhook events return the same data and format that you will receive via API calls for the same resources, allowing you to use the same code to handle both.

## How to set up webhooks

Webhooks can be configured via the Webhook Portal, which is accessed via a unique generated link for your application. To generate the link, make an [authenticated](/docs/auth) request to the Webhook Portal endpoint. The response will contain a link you can open in a web browser to access the portal.

For more information about how to use the portal, please consult the [documentation for Svix](https://docs.svix.com/receiving/using-app-portal/event-catalog), the platform which powers our webhooks.

## Limitations of webhooks

It is important to remember that webhooks are a fundamentally unreliable mechanism. We will automatically retry failed event messages, and you can manually replay messages that have failed [via the portal](https://docs.svix.com/receiving/using-app-portal/replaying-messages). However, given the possibility of errors or downtime for our systems, your systems or third parties between us, we can never 100% guarantee that all webhook events will be delivered successfully. You should always have a fallback system which can pull data via direct API requests.