HTTP

logiccloud Control can use an HTTP/REST endpoint as a data source. You define one or more requests against a base URL, map response data to your program variables (and program variables into request payloads), and authenticate with Basic, Bearer-token, or API-key credentials. This connector is the same one used for REST/RPC integrations.

Create a new HTTP connection

Add an HTTP / REST-RPC connection and enter the endpoint information. After the connection has been created, select it in the outline tree to edit its configuration.

Connection settings:

• Name: name of the connection
• Description: description, optional
• Base URL: the base URL that requests are issued against
• Authentication Type: None, Basic (username + password), Bearer (token), or API Key (key name, value, and location — header, query, or cookie)
• Headers: optional default request headers (key/value list)

Advanced connection options cover HTTP behavior: connection-pool limits, idle and timeout settings, TLS verification (TLS Insecure Skip Verify, TLS Server Name), and redirect handling (Follow Redirects, Maximum Redirects).

Note

The connector issues outbound requests only. It does not expose an inbound endpoint that receives requests, and it does not perform a separate login call to obtain and refresh a token — supply the bearer token or API key directly on the connection.

Mapping process variables

Each request maps process variables to the request payload and/or extracts values from the response. The mapping grid exposes:

• Variable: the program variable that is mapped
• Type: data type of the variable
• Value Path / Path / Key Path / Key Name: the location of the value (and, where applicable, its key) within the JSON request or response

Whether a request sends or receives a payload is determined by the request’s configured send/receive payload type, not by a per-mapping direction column.