Overview
This node interacts with the HttpBin API to perform 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, simulating API calls that require deletion of resources with optional parameters.
Common scenarios include:
- Testing REST APIs that accept DELETE requests with query parameters.
- Sending JSON payloads in DELETE requests where the API expects a body.
- Debugging how an API handles different types of input data on DELETE endpoints.
Example: Deleting a resource identified by query parameters or sending additional metadata in the JSON body during deletion.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Select type of data to send: Query (query parameters) or JSON (JSON body). |
| Query Parameters | Key-value pairs representing the query parameters to include in the DELETE request URL. |
| JSON Object | Key-value pairs representing the JSON properties to include in the DELETE request body. |
Output
The node outputs JSON data returned from the HttpBin API after performing the DELETE request. The output JSON typically contains details about the request received by HttpBin, such as headers, args (query parameters), and data (body content).
If binary data were supported, it would represent the raw response content, but this node focuses on JSON responses.
Dependencies
- Requires access to the public HttpBin API at
https://httpbin.org. - Optionally uses an API key credential if configured, though not mandatory.
- No other external dependencies are required.
Troubleshooting
- Issue: Incorrect or missing query parameters or JSON body keys may cause unexpected API responses.
- Resolution: Ensure all required keys and values are correctly set in the node's properties.
- Issue: Network errors or inability to reach
https://httpbin.org.- Resolution: Check internet connectivity and firewall settings.
- Issue: Unexpected response format or empty output.
- Resolution: Verify the selected "Type of Data" matches the API expectations and that the data is properly formatted.