HTTP In

Creates to an HTTP endpoint that can be used to create web services.

Use

This node creates a HTTP endpoint that responds to GET requests. Any flow that you start with an HTTP in node must be connected to an HTTP response node. Otherwise requests will time-out.

Properties

AttributeValuesRemarks
MethodGET|POST|PUT|DELETE|PATCHDefault is GET.
URLthe API endpointEnter the path relative to /api.
Nameany stringEnter a self-explaining name of the node. If you leave this field empty, the generic name displays in the dashboard.

Example

A simple HTTP API health check.

HTTP Response

Sends a response to a HTTP request received from an HTTP in node in the same flow. 

Use

Use this node together with an HTTP in node. If the HTTP in node receives a request, the flow is deployed. Use a Function node, a Template node or any other nodes between the HTTP in and the HTP response to create messages that are returned. The message must be passed to the HTTP response node in the msg.payload.

Properties

AttributeValuesRemarks
Nameany stringEnter a self-explaining name of the node. If you leave this field empty, the generic name displays in the dashboard.
Statuscodeany integerEnter the status code according to the API definition.
Headersselect type and valueEnter optional headers.

Example

Authentication

HTTP Request

Sends a GET request to another microservice and returns a JSON response.

Use

This node sends a GET request to an API endpoint. The returned JSON response can be parsed to a JSON object. Optionally, the payload that this node receives from other nodes can be appended to the query string parameters or sent as request body.

The HTTP request node must be used to call a Business logic function in a flow. 

Properties

AttributeValuesRemarks
MethodGET|POST|PUT|DELETE|PATCHDefault is GET.
URLthe API endpointEnter the absolute path.
Payloadselect from drop-down
  • Ignore: Ignores the msg.payload received from other nodes.
  • Append to query string parameters: Creates attribute/value pairs from the msg.payload and appends them to the query string.
  • Send as request body: Uses the msg.payload as is and passes it to the request body.
Enable secure (SSL/TLS) connectiontrue|falseDefault is false. If set to true, enter the key and certificate.
Use authenticationtrue|falseDefault is false. If set to true, enter credentials.
Enable connection keep-alivetrue|falseDefault is true.
Use proxytrue|falseDefault is false. If set to true, enter the proxy configuration.
Nameany stringEnter a self-explaining name of the node. If you leave this field empty, the generic name displays in the dashboard.

Example

Call a Knative business logic function.