Web Request
Provides a generic HTTP client for invoking web services that do not require OpenAPI or WSDL metadata. Supports simple REST-style requests for lightweight integrations and utility calls, with support for streaming bodies and optional authentication headers.
Revision History
1.0.0.3 - 2025/12/02 - Initial release.
Setup Notes
- Use connection-level headers for values shared across requests (for example: Authorization or Content-Type).
- Configure proxy settings on the connection when routing traffic through an outbound proxy is required.
- Provide absolute URLs in
Pathto bypass the base URL when calling external endpoints.
Connection
| Parameter | Type | Description |
|---|---|---|
Base URL |
String | Optional base URL applied to relative paths in requests. |
Authentication Type |
String | Authentication mode (for example: None, Basic, API Key, or Bearer Token). |
Username |
String | Username used for Basic authentication when applicable. |
Password |
Masked | Password used for Basic authentication when applicable. |
API Key Header |
String | Header name used when supplying an API key. |
API Key |
Masked | API key value sent with requests. |
Default Headers |
Object | Optional dictionary of headers applied to every request. |
Functions
Requests
Executes HTTP methods including GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, TRACE, and CONNECT. Payloads are streamed when provided to avoid buffering large bodies.
| Parameter | Type | Notes |
|---|---|---|
Connection |
Connection | Connection profile with endpoint and authentication details. |
Method |
String | HTTP method to execute. |
Path |
String | Relative or absolute path. Absolute URLs override Base URL. |
RequestHeaders |
String | Optional raw headers (key-value pairs) merged with connection defaults. |
RequestBody |
Stream | Optional request body stream; leave empty for methods that do not send a body. |
| Return | Type | Notes |
|---|---|---|
Response |
StreamingHttpResponse | Streaming HTTP response containing status code, headers, body stream, and request metadata. |
Known Issues
- TLS client certificates are not supported by this node.
- Large bodies should be streamed via
RequestBodyto avoid buffering.