HTTP endpoints

Each application you want to integrate with is represented by an HTTP endpoint. An endpoint provides a simple way to define the base URL and authentication credentials to use when making HTTP requests from a transformation script in the Integration Builder or a step in Flow Designer. For more information on using endpoints in Flow Designer, see Flow Components

If you are sending requests to an HTTPS endpoint, you must select the option to Trust self-signed certificates when configuring an endpoint.

Configure HTTP endpoints

By configuring endpoints separately, you can quickly modify all references to an endpoint across a workflow rather than editing each instance of the target URL in each script.

Endpoints should refer to the base IP address and port, or hostname of the target system; an additional parameter within the scripts can append any necessary paths, and allow you to target different locations at the same endpoint.

Endpoint authentication

Integration endpoints can be defined to support basic and OAuth 2.0 authentication. Customized OAuth 2.0 endpoints are available for BMC Remedy, Microsoft Graph API, Salesforce, ServiceNow, and Slack.

Configuring an endpoint with the required configuration and credentials for OAuth 2.0 authentication simplifies the transformation script for making HTTP requests to an API secured with OAuth 2.0. When using an OAuth 2.0 endpoint, the transformation script does not need to include reference to the access token URL, or any of the OAuth 2.0 fields associated with the endpoint.

Exported workflows do not include any OAuth information; all authorization content is cleared, and endpoints are set to "No Authorization".