# Twilio Errors Integration

Twilio's Debugger webhook notifies you in real time whenever an error or warning occurs in your Twilio account — a failed SMS delivery, an invalid API request, a webhook timeout, or any other issue Twilio detects while processing your traffic.

This integration forwards those notifications to ITOC360, opening an alert every time Twilio records a new error or warning event.

### How It Works

Twilio fires an HTTP POST request to your configured webhook URL each time a Debugger event occurs. The payload includes the event's severity level (`ERROR` or `WARNING`), a unique event identifier, and a nested JSON object with product-specific details such as the affected resource SID and error code. ITOC360 receives this payload and creates an alert immediately.

### Prerequisites

* A Twilio account
* Your ITOC360 webhook URL, generated when you create the integration

### In ITOC360

Go to **Sources**, click **Create Source**, and select **Twilio Errors** from the list. Copy the webhook URL that appears — you'll need it in the next step.

### In Twilio

#### Step 1 — Open the Debugger Webhook Settings

In the Twilio Console, click the **Monitor** tab. In the left sidebar, expand **Logs → Errors**, then click **Webhook**.

Paste your ITOC360 webhook URL into the **Webhook URL** field and click **Save**.

<figure><img src="https://4108595529-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FimJRSa33y5Ej6rwXrBeA%2Fuploads%2F7vfzu5AmsvAzS73UgCFr%2Fimage.png?alt=media&#x26;token=db870083-b889-4657-a93e-f4d151a1792e" alt=""><figcaption></figcaption></figure>

***

### Alert Behavior

| Level     | itoc360 Action | Priority |
| --------- | -------------- | -------- |
| `ERROR`   | Opens an alert | HIGH     |
| `WARNING` | Opens an alert | MEDIUM   |

Twilio Errors does not send a recovery payload — alerts opened by this integration remain open until you resolve them manually in ITOC360.

### Notes

* Every individual error or warning event creates a separate alert. If your account generates high error volumes, consider using **Twilio Alarms** instead — it aggregates errors over a time window and notifies only when a threshold is exceeded, reducing noise.
* The `Payload` field in each webhook contains a JSON string with product-specific details like the error code and affected resource SID. This data is visible in the alert metadata inside itoc360.
* Twilio recommends migrating to **Twilio Event Streams** for more scalable error monitoring. The Debugger webhook remains fully functional but Event Streams provides more flexibility for high-volume accounts.