@@ -29,5 +29,3 @@ Both API Invokers and Providers can subscribe to the **SERVICE_API_AVAILABLE** a
Additionally, if the *enhanced_event_report* function is supported, the API description could be received as event details in the eventDetails field if *apiStatusMonitoring* is also enabled. This will make it easier for event subscribers to know if any changes have been made to the API, such as a change in API availability to other AEFs.
@@ -32,5 +32,3 @@ Depending on the event you subscribe to, you can use one or more of these lists.
In cases where 2 or 3 lists are specified simultaneously for an event, notifications will only be sent when there is at least one matching element in each of the subscription lists. For example, if you subscribe to the ***ACCESS_CONTROL_POLICY_UPDATE*** event using the ***apiIds*** and ***apiInvokerIds*** filter lists, you will only be notified when the access control policy update corresponds to an API in the ***apiIds*** list and an invoker in the ***apiInvokerIds*** list at the same time.
@@ -18,6 +18,4 @@ To use this feature, the supported feature **enhancedEventReport** must be enabl
Using these fields provides significant benefits, such as enabling precise control over event notifications or ensuring that users receive the information when they need it. This flexibility allows for optimized resource usage, as unnecessary notifications are avoided, and the subscription can be tailored to specific use cases, improving overall efficiency and user satisfaction.
