Configuring the Named Credential on IP helps in preventing hardcoding of endpoint URL on the http action directly and some deployment issues as well, if the endpoint URL is environment specific.
Also configuring the APIs on the Named Credentials takes care of Endpoint Authorizations with salesforce security standards.
To use Named Credentials on the HTTP action of the IP, perform the following tasks:
1. Create the named credential by providing the Name, Label and End Point URL. Provide the base URL here, so that, while deploying the IPs we can prevent the hardcoding of URLs specific to the environment. If the endpoint URL has input parameters to be passed, then we can add those in the http action element of the IP.
For Example, an endpoint URL is:
Here, if recordId needs to be passed to the endpoint dynamically, then on Named Credentials, we can add the endpoint till https://dev.api.domain.org/dev-provider-exp-api and /members/recordId/details can be added on IP.
2. As per the requirement, provide the Authentication details and create the named credential.
3. Then on the http action of the IP, the expected Method like GET, POST etc can be added on “HTTP Method” and we can add the %% mergefield to pass the URL parameter dynamically on “HTTP Path”. The respective Named Credential will be configured on “Named Credential”. Headers and Input Parameters can be added additionally if needed.
Comments