# When webhooks are triggered

## When webhooks are triggered
- **Incoming calls**: When a call arrives on a service configured with a webhook URL. Services using static SVAML behavior (`STATIC`) do not trigger this webhook.
- **Call events**: When the service is configured with a webhook URL **and** the SVAML command does not have an `events` property defined. If the `events` property is present — even if empty — no webhook is triggered for that command's events. For example, a `dial` command with no `events` property will trigger a webhook when the call is answered; a `dial` command with `events: {}` will not.
- **Custom events**: When a `webhook` SVAML command is executed explicitly during a call.

Version: 2.0.58
Security: BasicAuth, SinchOAuth2

## Description:

  - `When webhooks are triggered` ()
    Incoming calls: When a call arrives on a service configured with a webhook URL. Services using static SVAML behavior (STATIC) do not trigger this webhook.Call events: When the service is configured with a webhook URL and the SVAML command does not have an events property defined. If the events property is present — even if empty — no webhook is triggered for that command's events. For example, a dial command with no events property will trigger a webhook when the call is answered; a dial command with events: {} will not.Custom events: When a webhook SVAML command is executed explicitly during a call.