Chapter 9. Connect to HTTP and HTTPS endpoints
In an integration, you can connect to HTTP and HTTPS endpoints to execute the
PATCH method. To do this, create an HTTP or HTTPS connection and then add it to an integration. The following topics provide details:
9.1. Create a connection to an HTTP or HTTPS endpoint
In an integration, to execute the HTTP
PATCH method, create a connection to an HTTP or HTTPS endpoint. You can then add the connection to one or more integrations.
You must know the URL for the endpoint that you want to connect to.
- In Fuse Online, in the left panel, click Connections to display any available connections.
- In the upper right, click Create Connection to display Fuse Online connectors.
- If you want to use Hyper Text Transfer Protocol to connect to the endpoint, then click the HTTP connector. If you want to use Secure Hyper Text Transfer protocol, then click the HTTPS connector.
In the Base URL field, enter the endpoint path. For example,
- Click Validate. Fuse Online immediately tries to validate the connection and displays a message that indicates whether validation is successful. If validation fails, revise specification of the base URL and try again.
- If validation is successful, click Next.
In the Connection Name field, enter your choice of a name that helps you distinguish this connection from any other connections. For example, enter
HTTPS My Company Sales.
- In the Description field, optionally enter any information that is helpful to know about this connection.
- In the upper right, click Create to see that the connection you created is now available. If you entered the example name, you would see that HTTPS My Company Sales appears as a connection that you can choose to add to an integration.
9.2. Add an HTTP or HTTPS connection to an integration
You can add an HTTP or HTTPS connection to any number of integrations.
You created an HTTP or HTTPS connection.
Do one of the following:
- To start an integration by periodically invoking an HTTP or HTTPS endpoint, add an HTTP or HTTPS connection as the integration’s start connection.
- To finish an integration by invoking an HTTP or HTTPS endpoint once, add an HTTP or HTTPS connection as the integration’s finish connection.
- In the middle of an integration, to invoke an HTTP or HTTPS endpoint once, add an HTTP or HTTPS connection after the start connection and before the finish connection.
If you are creating an integration, Fuse Online prompts you to choose and configure the start connection, and then choose and configure the finish connection. To add a middle connection, hover over the plus sign in the left panel at the location where you want to add the connection, and select Add a connection.
- Click the HTTP or HTTPS connection that you want to add to the integration.
Select the action that you want the connection to perform:
- If you are adding a start connection, then Periodic invoke URL is the only available action. This action invokes the endpoint at intervals that you specify and triggers the integration if the endpoint returns any data.
- If you are adding a finish or middle connection, then Invoke URL is the only available action. This action invokes the endpoint once.
- In the URL Path field, specify the location of the endpoint that you want to invoke.
In the HTTP Method field, select the method that you want the connection to perform. The default method is
GETobtains the content at the URL path.
PUTreplaces the content at the URL path with the integration data.
POSTstores the integration data at the URL path to create new content.
DELETEremoves content at the URL path.
HEADobtains metadata about the content at the URL path.
OPTIONSobtains communication option settings at the URL path.
TRACEobtains information for testing and diagnostic purposes.
PATCHpartially updates the content at the URL path according to the integration data.
- If you are adding a start connection, which periodically invokes the URL, then in the Period field, accept the default interval of 1 second or specify a number and its unit (milliseconds, seconds, minutes, or hours) to indicate how long to wait between invocations.
- Click Done to specify the action’s input or output type.
In the Select Type field, if the data type does not need to be known, accept Type specification not required and then, at the bottom, click Done. You do not need to follow the rest of these instructions.
Otherwise, select one of the following as the schema type:
JSON schema is a document that describes the structure of JSON data. The document’s media type is
JSON instance is a document that contains JSON data. The document’s media type is
XML schema is a document that describes the structure of XML data. The document’s file extension is
XML instance is a document that contains XML data. The document’s file extension is
- JSON schema is a document that describes the structure of JSON data. The document’s media type is
In the Definition input box, paste a definition that conforms to the schema type you selected. For example, if you select JSON schema then you would paste the content of a JSON schema file, which has a media type of
In the Data Type Name field, enter a name that you choose for the data type. For example, suppose you are specifying a JSON schema for vendors. You can specify
Vendoras the data type name.
You will see this data type name when you are creating or editing an integration that uses the connection for which you are specifying this type. Fuse Online displays the type name in the integration visualization panel and in the data mapper.
- In the Data Type Description field, provide information that helps you distinguish this type. This description appears in the data mapper when you hover over the step that processes this type.
- Click Done.
The connection appears in the integration flow in the location where you added it.