+

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

Protocol

Protocol that the endpoint supports.

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 EDI, JSON, or XML 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?name=something

x

Connection Idle Timeout (milliseconds)

Connection idle timeout period in milliseconds. The default is 30000.

x

Response Timeout (milliseconds)

Maximum time, in milliseconds, for which the request element blocks the execution of the flow that is waiting for the HTTP response.

Authentication Settings

Depending on how you set up your authentication policy, refer to the appropriate authentication type and descriptions here.

Authentication Type Description

None

No authentication

API Key

  • HTTP Header Name
    The HTTP header parameter associated with the API Key value.

  • API Key
    The value for the access key you set.

Basic

Specifies a simple authentication policy that protects the API by requiring a username and password when calling apps to make a request.

  • Username
    The username you created for this authentication policy

  • Password
    The password you created for this authentication policy

Client Credentials

  • Client ID
    The client ID provided when registering your application

  • Client Secret
    The client secret provided when registering your application

  • Client Header
    The client header

  • Client Secret Header
    The client secret header

OAuth Token

  • Token URL
    The authorization URL.

  • Client ID
    The client ID provided when registering your application

  • Client Secret
    The client secret provided when registering your application

Was this article helpful?

💙 Thanks for your feedback!

View on GitHub