Overview
This node interacts with the HttpBin API, specifically allowing you to perform HTTP DELETE requests with customizable data payloads. It is useful for testing and debugging HTTP DELETE operations by sending either query parameters or JSON body data to the HttpBin service, which then echoes back the request details.
Practical examples include:
- Testing how your application handles DELETE requests with specific query parameters.
- Sending JSON data in a DELETE request to simulate API interactions.
- Debugging HTTP client behavior by inspecting the echoed response from HttpBin.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Choose the type of data to send with the DELETE request: either Query parameters or JSON body data. |
| Query Parameters | When "Type of Data" is set to Query, specify one or more key-value pairs as query parameters to be sent in the URL. |
| JSON Object | When "Type of Data" is set to JSON, specify one or more key-value pairs as JSON properties to be sent in the request body. |
Output
The node outputs the JSON response returned by the HttpBin API. This response typically contains an echo of the request made, including the URL, headers, query parameters, and JSON body (if any). This allows users to verify exactly what was sent in the DELETE request.
No binary data output is produced by this node.
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 are needed beyond standard HTTP request capabilities.
Troubleshooting
Common issues:
- Incorrectly formatted query parameters or JSON body may cause unexpected responses.
- Network connectivity problems will prevent reaching the HttpBin API.
- Selecting the wrong "Type of Data" option may result in data being sent in an unintended format.
Error messages:
- HTTP errors (e.g., 4xx or 5xx) indicate issues with the request or server availability.
- JSON parsing errors may occur if the input data is malformed; ensure keys and values are properly specified.
To resolve these issues:
- Double-check the key-value pairs for correctness.
- Verify network connectivity.
- Confirm that the "Type of Data" matches the intended payload format.