2 NEF Configuration Using REST APIs

This chapter provides information about how to configure Oracle Communications Cloud Native Core, Network Exposure Function (NEF) using REST APIs.

NEF can be configured using Helm and REST configurations. Some configurations are performed during NEF installation using Helm and a few configurations are modified using REST APIs. REST configurations can also be performed using the Oracle Communications Cloud Native Configuration Console (CNC Console).

For more information about NEF configuration types, see the following guides:

• For Helm configuration: Oracle Communications Cloud Native Core, Network Exposure Function Installation, Upgrade, and Fault Recovery Guide.
• For REST configurations using the CNC Console: Oracle Communications Cloud Native Core, Network Exposure Function User Guide.

NEF uses GET, PUT, DELETE, and so on HTTP methods to retrieve, update, and remove REST API configuration data.

Note:

• The PUT method for multiple rules as a single payload through a single API is not allowed unless specified explicitly.
• If the query parameter is incorrect, NEF does not return an error response but considers an API call without any query parameter, and therefore the GET ALL output is returned in the response.
• The CAPIF or NEF configuration Rest API's do not support any semantic validation for every field. It is operator's responsibility to populate valid values in the Rest API and CNC Console.