Skip to Content

HTTP Connector


The HTTP connector establishes access to an HTTP server through a RESTful web service (REST API).

The HTTP connector provides an interface for creating an HTTP connection, the foundation used for generating instances of HTTP activities. These activities, once configured, interact with an HTTP server through the connection.

The HTTP connector is accessed from the design component palette's Project endpoints and connectors tab (see Design Component Palette).


With the release of the HTTP v2 connector, we recommend converting existing HTTP connections and activities to HTTP v2. Learn more about the benefits of the HTTP v2 connector in our HTTP v2 blog post or see a comparison of HTTP and HTTP v2 connector features.

Jitterbit's long-term intention is to deprecate the HTTP connector, which will be announced in accordance with Jitterbit's End-of-Life Policy. At present, there is no timeline for deprecation and the HTTP connector remains fully supported. We recommend that you convert existing HTTP connections and activities to HTTP v2 when possible.

Connector Overview

This connector is used to first configure an HTTP connection. Activity types associated with that connection are then used to create instances of activities that can be used as sources (to provide data) or targets (to consume data) in an operation or a script.

Whether an activity instance can be used as a source or a target depends on whether the web service requires a structured request or returns a structured response. Each activity instance is configured with request and response schemas using user-provided custom schemas.

Together, a specific HTTP connection and its activities (GET, PUT, POST, DELETE, or Custom) are referred to as an HTTP endpoint:

HTTP activities


If you experience issues with the HTTP connector, these troubleshooting steps are recommended:

  1. Ensure the HTTP connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.

  4. If using Private Agents, you can check the agent logs for more information.