This node can be used to issue a HTTP PATCH requests. A PATCH request is considered a set of instructions on how to modify a resource. Contrast this with PUT; which is a complete representation of a resource.
The node allows you to either send a request to a fixed URL (which is specified in the dialog) or to a list of URLs provided by an optional input table. Every URL will result in one request which in turn will result in one row in the output table. You can define custom request headers in the dialog.
The sent data is usually taken from a column of the input table but you can also provide a constant value in the dialog instead.
By default the output table will contain a column with the received data, its content type, and the HTTP
status code. The node tries to automatically convert the received data into a KNIME data type based on its
content type. In case no automatic conversion is possible, binary cells will be created.
You can extract additional response headers into column by defining them in the dialog.
The node supports several authentication methods, e.g. BASIC and DIGEST. Other authentication methods may be provided by additional extensions.
The node supports the Credential port as input (see dynamic input ports). If the port is added, it must supply a Credential that can be embedded into the HTTP Authorization header, and all request done by the node will use the Credential from the port, regardless of other node settings. The OAuth2 Authenticator nodes provide such a Credential for example.
3xx
).File > Preferences > General > Network Connections
.Basic
authentication for proxy hosts.Basic
authentication for proxy hosts.Accept
or X-Custom-Key
. Note that some
header keys such as Origin
are silently ignored by default for security reasons. You can configure
KNIME AP to allow any header key by setting the sun.net.http.allowRestrictedHeaders
system property in the
knime.ini configuration file to true
.You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
To use this node in KNIME, install the extension KNIME REST Client Extension from the below update site following our NodePit Product and Node Installation Guide:
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!Do you have feedback, questions, comments about NodePit, want to support this platform, or want your own nodes or workflows listed here as well? Do you think, the search results could be improved or something is missing? Then please get in touch! Alternatively, you can send us an email to mail@nodepit.com, follow @NodePit on Twitter or botsin.space/@nodepit on Mastodon.
Please note that this is only about NodePit. We do not provide general support for KNIME — please use the KNIME forums instead.