Overview
The node interacts with the HttpBin API, specifically supporting HTTP GET requests under the "HTTP Verb" resource. It allows users to send HTTP GET requests with customizable query parameters. This is useful for testing and debugging HTTP requests by sending specific query parameters and observing the response from HttpBin, a service designed for HTTP request & response inspection.
Practical examples include:
- Testing how an API handles various query parameters.
- Debugging URL encoding issues.
- Inspecting the structure of query parameters sent in a GET request.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the type of data to send; currently only supports "Query" (query parameters). |
| Query Parameters | A collection of key-value pairs representing the query parameters to be sent with the GET request. |
Output
The node outputs JSON data representing the response from the HttpBin API. The json output field will contain the full HTTP response body returned by HttpBin, which typically includes details about the request such as the query parameters received, headers, origin IP, and other metadata.
No binary data output is indicated or expected.
Dependencies
- Requires access to the public HttpBin API at https://httpbin.org.
- Optionally can use an API authentication token if configured, but it is not required.
- No additional external dependencies beyond standard HTTP request capabilities.
Troubleshooting
- Common Issues:
- Network connectivity problems preventing access to https://httpbin.org.
- Incorrectly formatted query parameters causing unexpected responses.
- Error Messages:
- HTTP errors (e.g., 4xx or 5xx) indicate issues with the request or server availability.
- Missing or malformed query parameters may result in incomplete or empty response fields.
- Resolutions:
- Verify network connection and endpoint accessibility.
- Double-check query parameter keys and values for correctness.
- Ensure that the "Type of Data" property is set correctly (currently only "Query" supported).