Skip to end of metadata
Go to start of metadata


An HTTP connection is configured using the HTTP connector, establishing access to an HTTP or HTTPS web service (including RESTful web services). Once a connection is established, you can configure one or more HTTP activities associated with that connection to be used either as a source to provide data to an operation or script, or as a target to consume data in an operation or script.

Creating or Editing an HTTP Connection

From the design canvas, open the Connectivity tab of the design component palette:

To configure a new HTTP connection, use the Show dropdown to filter on Connectors, and then click the HTTP connector block:

To configure an existing HTTP connection, use the Show dropdown to filter on Endpoints, and then double-click the HTTP connection block:

These open the configuration screen for the HTTP connection, covered next.

Configuring an HTTP Connection

Configuration of an HTTP connection includes these fields:

TIP: Fields with a variable icon support using global variablesproject variables, and Jitterbit variables. Begin either by typing an open square bracket [ into the field or by clicking the variable icon to display a list of the existing variables to choose from.

  • Endpoint Name: Enter a name to use to identify the HTTP connection. The name must be unique for each HTTP connection and must not contain forward slashes (/) or colons (:). This name is also used to identify the HTTP endpoint, which refers to both a specific connection and its activities.
  • Base URL: Enter a valid base URL for the connection. To use SSL encryption, simply use https:// in the URL. Do not include any query parameters or paths unless they will be used for all associated activities (You will be able to specify unique paths and parameters during activity configuration.). The final URL will be concatenated from the Base URL provided here along with any paths specified during activity configuration. 

  • Username and Password: If applicable, enter a username and password that will allow access to the HTTP server. You can leave these fields blank for anonymous authentication if no username or password is required.

  • Certificate: Use the dropdown to select an available certificate to authenticate with the HTTP server. You can manage client-side SSL certificates from the Management Console under Customizations > Client Certificates.

  • Retry: Functional only when using an environment associated with a Private Agent Group, this setting is used to retry a request when an HTTP endpoint returns one of these status codes: 500, 501, 502, 503, or 504.

    In order for this setting to take effect, Private Agents must be version 10.22 or later. With earlier agent versions, the configuration of this setting is ignored.

    Select the Retry checkbox to expand additional configuration options:

    • Retry Interval (Seconds): Enter the number of seconds (maximum of 5 seconds) to wait between resending a request to the HTTP endpoint.
    • Max Retries: Enter the number of times (maximum of 5 retries) that a request will be resent to the HTTP endpoint. If the request still fails after the maximum number of retries, an exception with an error message will be returned in the operation log. In addition, the Private Agent will log each retry in the jitterbit.log log file.

      Each retry is treated as part of the same operation run, where only a single record appears in the operation log. Any operation actions configured to run downstream operations are triggered based on the end status of the operation after retrying up to the maximum number of retries.

  • Optional Settings: Click to expand additional optional settings:

    • Security Option: If applicable, select Use Basic HTTP Authentication to authenticate with the host using basic HTTP authentication without SSL encryption. Note that if this option is used, the provided password is sent in clear text. (Unless required, this is not recommended.)

      If this option is not used, by default Jitterbit Harmony negotiates with the endpoint to determine which authentication methods are supported, and uses the provided credentials against one of the protocols. In addition to HTTP Basic, Jitterbit Harmony supports these HTTP authentication options:

      • HTTP Digest

      • HTTP Digest with authentication with an IE flavor

      • HTTP NTLM

    • Ignore Lines: If there are headers and/or footers in the source data that you want to be ignored, enter the number of lines to ignore in the First and Last fields.

    • Proxy Settings: If you want to specify a custom proxy, use the dropdown to select one of these options:

      • Default: Proxy settings are enabled, using the Private Agent proxy configuration if one exists. If proxy settings are not specified in the agent configuration, then the Default setting has the same result as the Disable setting.

      • Disable: Proxy settings are disabled for this specific connection, bypassing the Private Agent proxy configuration if one exists.

      • Custom: Proxy settings are enabled for this specific connection using custom information provided here. This option bypasses the Private Agent proxy configuration if one exists, and instead uses custom proxy information. When Custom is selected, additional fields become available for you to configure. For details on these fields, see Enabling Proxy for Private Agents.

    • Advanced HTTP Properties: If applicable, set these advanced options:

      • Content-Type: Enter the content-type of the request structure that is expected by the particular API. If the method being used does not accept structured data, or if the API does not require the content-type to be specified, you can leave this field blank. Examples of content-types include text/plain, application/jsonapplication/x-www-form-urlencoded, etc.

      • Enable Content Encoding: If selected, the Accept-Encoding header is sent with the encoding supported by Jitterbit Harmony. Currently Gzip is supported.

      • Enable Chunked Transfer Encoding: If selected, the Transfer-Encoding: chunked header is sent. Use this option if you are transferring large data sets.

      • Send Expect 100-continue: If selected, the Expect: 100-continue header is sent. With this option, no data is sent until the HTTP server has validated the headers. Use this option if you are sending large amounts of data but don't want to use chunked transfer encoding.

      • Allow Weak Ciphers: Select this checkbox to communicate with HTTP servers that use weak ciphers (DES/3DES and RC4).

      • HTTP Accept Encoding Gzip: Selected by default, this option tells the HTTP server that Jitterbit Harmony can accept a Gzip-compressed response. In return, Harmony follows the RFC 1952 standard and automatically decompresses Gzip HTTP responses. If the server does not use Gzip, Harmony sees that the response is not compressed and handles it as usual.

        NOTE: This setting is unrelated to the Gzip connector.
      • Only Applicable When Using HTTPS: Use the dropdown to select a specific SSL version if the HTTP server requires it. The default is Negotiate.

      • Request Headers (One Line per Header): Any text entered in this box is sent as an HTTP header. Specify each header on one line unless the header is wrapped according to the HTTP standard. This field also supports using global variablesproject variables, and Jitterbit variables by replacing variables in square brackets [ ] with their values.

  • Test: Click to verify the connection by sending an HTTP GET request with no authorization. 
  • Save Changes: Click to save and close the connection configuration.
  • Discard Changes: After making changes to a new or existing configuration, click to close the configuration without saving. A message asks you to confirm that you want to discard changes.
  • Delete: After opening an existing connection configuration, click to permanently delete the connection from the project and close the configuration (see Component Dependencies, Deletion, and Removal). A message asks you to confirm that you want to delete the connection.

Next Steps

After configuring an HTTP connection, you can configure one or more HTTP activities associated with that connection to be used either as a source (to provide data within an operation) or as a target (to consume data within an operation), or to be used in a script.

Use the Show dropdown to filter on Endpoints, and then click the HTTP connection block to display activities that are available to be used with an HTTP connection:

 For more information, see HTTP Activities, which covers GET, PUT, POST, DELETE, and Custom activities.

On This Page

Last updated:  Jan 05, 2021

  • No labels