Contact Free trial Login

HTTP and HTTPS Send Configuration

The HTTP and the secure HTTPS protocol send settings are used with endpoints for sending transmissions to your partner and endpoints that are targets at your organization.

Use the HTTP and HTTPS endpoint to:

  • Send to partners
    Send outbound EDI files to your trading partners in outbound message flows.

  • Target at host
    Send application messages (JSON or XML) to your backend applications in inbound message flows.

Name Description Required

Protocol

Select HTTP or HTTPS. The default is HTTPS.

Yes

Endpoint Name

Name used to easily identify the function of this endpoint. Names are automatically assigned, but can be overwritten.

Yes

Description

Describe a purpose and any other important details for this endpoint.

No

URL

Target HTTP service to which to send translated 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

Yes

Connection Idle Timeout (milliseconds)

The number of milliseconds that a connection can remain idle before it is closed. The default is 30000.

Yes

Response Timeout (milliseconds)

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

No

See Certificates for more information about configuring certificates in Anypoint Partner Manager.

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
    Header parameter associated with the API Key.

  • API Key
    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
    Username you set up with this authentication policy

  • Password
    Password you set up with this authentication policy

Client Credentials

  • Client ID
    Client ID provided when registering your application.

  • Client Secret
    Client secret provided when registering your application.

  • Client Header
    Add the client header.

  • Client Secret Header
    Add the client secret header.

OAuth Token

  • Token URL
    Enter a valid authorization URL.

  • Client ID
    Client ID provided when registering your application.

  • Client Secret
    Client secret provided when registering your application.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub