Overview
This node interacts with the HttpBin API, specifically performing HTTP DELETE requests. It allows users to send data either as query parameters or as a JSON body in the DELETE request. This is useful for testing and debugging HTTP DELETE operations by simulating requests to an endpoint that echoes back the sent data.
Common scenarios include:
- Testing how an API handles DELETE requests with query parameters.
- Sending JSON payloads in DELETE requests to APIs that support it.
- Debugging and inspecting HTTP DELETE request formats and responses.
Example: Deleting a resource identified by query parameters or sending a JSON object specifying deletion criteria.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Choose whether to send data as Query Parameters (queryParameter) or as a JSON Body (jsonData). |
| Query Parameters | When "Type of Data" is set to Query, specify one or more key-value pairs to be sent as URL query parameters in the DELETE request. |
| JSON Object | When "Type of Data" is set to JSON, specify one or more key-value pairs to be sent as a JSON body in the DELETE request. |
Output
The node outputs the response from the HttpBin API in the json field. This typically includes an echo of the request details such as headers, args (query parameters), and data (body content). The output structure helps verify what was sent and received.
No binary data output is indicated.
Dependencies
- Requires access to the public HttpBin API at
https://httpbin.org. - Optionally uses an API authentication credential if configured, but it is not required.
- No other external dependencies are needed.
Troubleshooting
- Issue: Incorrect or missing query parameters or JSON keys may result in unexpected API responses.
- Resolution: Ensure all required keys and values are correctly specified in the input properties.
- Issue: Network errors or inability to reach
https://httpbin.org.- Resolution: Check internet connectivity and firewall settings.
- Issue: Sending JSON data when the API expects query parameters (or vice versa) might cause unexpected behavior.
- Resolution: Verify the "Type of Data" property matches the expected format for your use case.