# Call Events

The **DIDWW Call Events API** allows to receive real-time **Call Events** and **CDRs** through a designated HTTP
endpoint. This webhook-based mechanism provides flexibility for developing applications that support near real-time call
processing, CDR retrieval, billing, and call tracking.

**Voice IN Call Events**

Receive real-time HTTP callbacks for inbound calls, covering start, connect, and end events.

[Voice IN Call Events](did-call-events.html)

**Voice OUT Call Events**

Receive real-time outbound call event data, including detailed CDRs, connection status, and call metrics via HTTP
callbacks.

[Voice OUT Call Events](termination-call-events.html)

**Voice IN CDR Streaming**

Receive near real-time inbound Call Detail Records (CDRs) after call completion for monitoring, reporting, and
analytics.

[Voice IN Service CDR Streaming](did-cdr.html)

**Voice OUT CDR Streaming**

Receive near real-time outbound Call Detail Records (CDRs) after call completion for billing, reporting, and performance
monitoring.

[Voice OUT Service CDR Streaming](termination-cdr.html)

Important

The **Call Events API** can only be enabled upon customer request by contacting the DIDWW Technical Support team at
[support@didww.com](mailto:support%40didww.com).

---



## Call Events Configuration

Call event configuration and management are available in the **API** > **Call Events API** section.

[![Call Events API](../_images/call_events_fig1.png)](../_images/call_events_fig1.png)


**Fig. 1.** Call Events section.

To configure the Call Events service, follow these steps:

1. **Open the Configuration Page**

   Select **CDR Streaming** or **Call Events** for **Voice IN** or **Voice OUT**, then click **Configure** in the **Call
Events API** page: [Call Event Configurations](https://my.didww.com/#/call_event_configs).

   > [![Configure Voice IN Call Events](../_images/call_events_fig2.png)](../_images/call_events_fig2.png)
   >
   >
   > **Fig. 2.** Call Events configuration window.
2. **Enter the Required Configuration Parameters**

   > | **Parameter** | **Description** |
   > | --- | --- |
   > | **Endpoint** | The URL where call event notifications will be delivered (e.g., https://example.com/). |
   > | **Enable GZIP Compression** *(Optional)* | If enabled, HTTP data is compressed before being sent. |
   > | **Authentication** *(Optional)* | Use **Basic Authentication (Basic Auth)** with a username and password:  - **Username**   - The username associated with the endpoint URL. - **Password**   - The password associated with the endpoint URL. |
   > | **Headers** *(Optional)* | Define custom HTTP headers.  **Examples:**  - **X-Auth-Token**   - Secure authentication token used for verifying requests (e.g., your\_secure\_token). - **X-Client-ID**   - Unique identifier for the client or application sending the request (e.g., unique\_client\_identifier). |
3. **Save the Configuration**

   Click **Submit** to finalize the setup and activate call event delivery.

---



### Call Events IP addresses

Call event requests are sent from the following IP addresses:

> - **IPv4:** 46.19.210.148
> - **IPv6:** 2a01:ad00:2:3::148

Ensure that these IP addresses are whitelisted in your receiving system.

---



### Call Events Request format

Call Events are delivered as HTTP **POST** requests to your configured endpoint.
The request payload structure varies based on the service type (Voice IN or Voice OUT).

Ensure your endpoint is configured to:

> - Accept **JSON-formatted** payloads (optionally gzip-compressed).
> - Validate event types (start, connect, end).
> - Parse timestamps, caller/callee numbers, and unique call identifiers for tracking.

For full details on payload schemas, supported attributes, and processing best practices, refer to the related API
documentation.