Contact Us 1-800-596-4880
  1. Homepage
  2. Partner Manager (2.x)
  3. Message Flow Components
  4. Endpoints
  5. Send Endpoints

  6. HTTP and HTTPS Send Endpoint Settings

HTTP and HTTPS Send Endpoint Settings

HTTP and HTTPS send endpoint settings configure where to send B2B messages transmitted over HTTP or HTTPS, respectively. There are two types of HTTP and HTTPS send endpoints:

  • Send to Partners

    • Target endpoint in an outbound message flow through which transformed B2B messages are sent to the partners either directly or via a third-party connection

    • Acknowledgement endpoint in an inbound message flow

    A host, partner, or third-party connection can own HTTP and HTTPS Send to Partners endpoints.

  • Target at Host

    Target endpoint in an inbound message flow through which transformed messages are sent to the backend applications.

    Only a host can own HTTP and HTTPS Target at Host endpoints.

Create HTTP and HTTPS send endpoints by configuring these settings on the host, partner, or third-party connection page. You can also create these endpoints when you configure an outbound message flow.

Name Description Required

Owner

Host, partner, or third-party connection that owns the endpoint.

x

Usage

Endpoint function (Send to partners or Target at host).

x

Protocol

Protocol that the endpoint supports (HTTP or HTTPS).

x

Endpoint Name

Automatically generated name used to identify the endpoint, which you can subsequently modify manually.

x

Description

User-supplied value that describes the purpose the endpoint.

URL

Target HTTP or HTTPS service to which to send transformed X12, EDIFACT, JSON, XML, or CSV messages. The URL must be accessible from the runtime environment that processes your B2B integrations. Enter a well-formed URL (including the path) that specifies where to send the request, for example: https://www.mulesoft.com/sendRequest

x

Response Timeout (in milliseconds)

Maximum time, in milliseconds, for the request element to block the execution of a flow that is waiting for the HTTP response. The default is 15000 milliseconds.

x

Retry interval (in seconds)

Frequency of reconnection attempts when unable to connect to the remote HTTP or HTTPS service. The default is 60 seconds.

x

Maximum retry attempts

Maximum number of reconnection attempts. To prevent Partner Manager from retrying after an initial connection failure, set this value to 0. The default is 3.

x

Authentication type

Authentication method used to protect the HTTP or HTTPS endpoint. Values are:

x

Certificate (TLS Context)

(Applies to HTTPS endpoints) SSL certificate. Values are:

  • Use CA-signed certificates

    Uses a certificate that was issued and signed by a certificate authority (CA). With this option, you don’t need to upload an additional certificate.

  • Use a self-signed certificate

    Uses a certificate that was not issued or signed by a CA. With this option, you must either select an existing certificate or upload a new certificate in <certifcate name>.PEM format.

  • Allow insecure connection

    Allows an insecure connection that doesn’t perform certificate validation.

x

API Key Authentication

Authentication type that requires a valid API key in the HTTP request header.

Use the following settings to configure API Key authentication:

Name Description Required

HTTP Header Name

HTTP header parameter associated with the API key value.

x

API Key

Value of the API key.

After saving your new or reconfigured endpoint, you cannot subsequently retrieve or modify the API key.

x

Certificate

Certificate to use for authentication.

Basic Authentication

Authentication type that requires a username and password in the HTTP or HTTP request header.

Use the following settings to configure Basic authentication:

Name Description Required

Username

Username to use when making a request.

x

Password

Password to use when making a request.

x

Client Credentials Authentication

Authentication type that requires a valid client ID and client secret in the HTTP or HTTPS request header.

Use the following settings to configure Credit Credentials authentication:

Name Description Required

Client ID header name

HTTP header name that the client ID uses to call the endpoint URL. Default is "client_id".

x

Client ID header value

HTTP header value for the client ID.

x

Client secret header name

HTTP header name for the client secret. Default is "client_secret".

x

Client secret header value

HTTP header value for the client secret.

x

OAuth Token Authentication

Authentication type that requires a valid OAuth token in the HTTP or HTTPS request header.

Use the following settings to configure OAuth Token authentication:

Name Description Required

Token URL

URL of the authentication server that provides access tokens.

x

Client ID

Client ID provided when registering your application with the authorization server.

x

Client Secret

Client secret provided when registering your application with the authorization server.

x

See Also