Overview
This node interacts with the HttpBin API, specifically performing HTTP DELETE requests. It allows users to send either query parameters or a JSON body as part of 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 various query parameters.
- Sending JSON payloads in DELETE requests to APIs that accept bodies on DELETE.
- Debugging client-server interactions involving DELETE methods.
Practical example:
- You want to test deleting a resource identified by query parameters, e.g.,
?id=123. - Or you want to send a JSON object
{ "id": 123, "force": true }in the body of a DELETE request.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Select the type of data to send with the DELETE request: - Query (query parameters) - JSON (JSON body) |
| Query Parameters | When "Type of Data" is set to Query, specify one or more key-value pairs to be sent as query parameters in the URL. Each pair consists of a Key and its corresponding Value. |
| JSON Object | When "Type of Data" is set to JSON, specify one or more key-value pairs to be sent as JSON properties in the request body. Each pair consists of a Key and its corresponding Value. |
Output
The node outputs JSON data representing the response from the HttpBin API after making the DELETE request. The structure typically includes fields that echo back the request details such as the URL, headers, query parameters, and JSON body sent. This helps verify what was actually transmitted.
No binary data output is produced by this node.
Dependencies
- Requires access to the public HttpBin API at
https://httpbin.org. - No mandatory credentials are required, but optionally an API authentication token can be configured if needed.
- Network connectivity to the HttpBin service must be available.
Troubleshooting
Issue: The node returns an error or no response.
- Cause: Network issues or HttpBin service downtime.
- Resolution: Check internet connection and try again later.
Issue: Query parameters or JSON body not reflected in the response.
- Cause: Incorrect property configuration or mismatch between "Type of Data" and provided inputs.
- Resolution: Ensure that when "Type of Data" is set to "Query", only query parameters are provided; similarly, provide JSON properties only when "Type of Data" is "JSON".
Issue: Malformed JSON or invalid keys/values.
- Cause: Input values may contain invalid characters or formatting.
- Resolution: Validate all keys and values before sending.