curl\_multi\_notify\_disable(3) Library Functions Manual curl\_multi\_notify\_disable(3)

# [NAME](#NAME)

curl\_multi\_notify\_disable - disable a notification type

# [SYNOPSIS](#SYNOPSIS)

```
#include <curl/curl.h>
CURLMcode curl_multi_notify_disable(CURLM *multi_handle,


                                    unsigned int notification);
```

# [DESCRIPTION](#DESCRIPTION)

Disables collecting the given notification type in the multi handle. A callback function installed via [*CURLMOPT\_NOTIFYFUNCTION(3)*](/man/os/curl/CURLMOPT_NOTIFYFUNCTION.3) is no longer called when this notification happens.

Only when a notification callback is installed *and* a notification is enabled are these collected and dispatched to the callback.

Several notification types can be enabled at the same time. Disabling an already disabled notification is not an error.

A notification can be enabled again via [*curl\_multi\_notify\_enable(3)*](/man/os/curl/curl_multi_notify_enable.3).

# [PROTOCOLS](#PROTOCOLS)

This functionality affects all supported protocols

# [EXAMPLE](#EXAMPLE)

```
int main(void)
{


  int rc;


  CURLM *multi = curl_multi_init();


  rc = curl_multi_notify_disable(multi, CURLMNOTIFY_INFO_READ);
}
```

# [AVAILABILITY](#AVAILABILITY)

Added in curl 8.17.0

# [RETURN VALUE](#RETURN_VALUE)

This function returns a CURLMcode indicating success or error.

CURLM\_OK (0) means everything was OK, non-zero means an error occurred, see [*libcurl-errors(3)*](/man/os/curl/libcurl-errors.3).

The return code is for the whole multi stack. Problems still might have occurred on individual transfers even when one of these functions return OK.

# [SEE ALSO](#SEE_ALSO)

[**CURLMOPT\_NOTIFYDATA**(3)](/man/os/curl/CURLMOPT_NOTIFYDATA.3), [**CURLMOPT\_NOTIFYFUNCTION**(3)](/man/os/curl/CURLMOPT_NOTIFYFUNCTION.3), [**curl\_multi\_notify\_enable**(3)](/man/os/curl/curl_multi_notify_enable.3)

2026-10-19 libcurl

---

Document: curl_multi_notify_disable(3) from curl 8.23.0-r1 (Chainguard OS)
Source: https://github.com/curl/curl.git