POST /webhooks

Create a webhook.

Servers

https://enode-api.production.enode.io

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/json"

Request body fields

Name	Type	Required	Description
`url`	String	Yes	The HTTPS URL that webhook payloads should be sent to.
`events[]`	Array	No	The events which will trigger the webhook. Available events: ``, `user:vehicle:discovered`, `user:vehicle:updated`, `user:vehicle:deleted`, `user:vehicle:smart-charging-status-updated`, `user:charge-action:updated`, `user:vendor-action:updated`, `user:schedule:execution-updated`, `user:charger:discovered`, `user:charger:updated`, `user:charger:deleted`, `user:hvac:discovered`, `user:hvac:updated`, `user:hvac:deleted`, `user:inverter:discovered`, `user:inverter:updated`, `user:inverter:deleted`, `user:credentials:invalidated`, `user:battery:discovered`, `user:battery:updated`, `user:battery:deleted`, `enode:webhook:test`, `user:meter:discovered`, `user:meter:updated`, `user:meter:deleted` Default value: [ "" ]
`authentication`	Object	No	If provided, the authentication header will be sent with each webhook request.
`authentication.headerValue`	String	Yes	Authentication header value.
`authentication.headerName`	String	Yes	Authentication header name.
`secret`	String	Yes	A cryptographically secure secret, generated and provided by your client. Refer to Generating a secret for details on how to do this.
`apiVersion`	String	No	If provided, webhook payloads will be generated for this version. If not provided or `null`, the default API version of the client will be used when generating webhook payloads. Valid versions: `2024-10-01`

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.