Overview
This node interacts with the HttpBin API, specifically performing HTTP DELETE requests. It allows users to send either query parameters or JSON data in the DELETE request. This is useful for testing and debugging HTTP DELETE operations by sending custom data and inspecting the response from HttpBin.
Practical examples include:
- Sending a DELETE request with specific query parameters to simulate deleting resources identified by those parameters.
- Sending a DELETE request with a JSON body payload to test APIs that accept JSON data on DELETE operations.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the type of data to send with the DELETE request: either Query Parameters or JSON Body. Options: "Query", "JSON". |
| Query Parameters | When "Type of Data" is set to Query, this property lets you specify multiple key-value pairs as query parameters to be appended to the URL. Each pair consists of a Key (parameter name) and Value (parameter value). |
| JSON Object | When "Type of Data" is set to JSON, this property lets you specify multiple key-value pairs as JSON properties to be sent in the request body. Each pair consists of a Key (property name) and Value (property value). |
Output
The node outputs the JSON response returned by the HttpBin API after performing the DELETE request. The output json field contains the full response data from HttpBin, which typically includes details about the request received by HttpBin such as headers, args (query parameters), json (body content), origin IP, and URL.
No binary data output is produced by this node.
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 additional environment variables or external services are needed beyond internet access.
Troubleshooting
Common issues:
- Incorrectly formatted query parameters or JSON body may cause unexpected responses or errors.
- Network connectivity issues will prevent reaching the HttpBin service.
- Selecting the wrong "Type of Data" option without providing corresponding data fields will result in empty or malformed requests.
Error messages:
- HTTP errors from HttpBin (e.g., 4xx or 5xx status codes) indicate issues with the request or server.
- Validation errors if required keys or values are missing in the input properties.
Resolutions:
- Ensure all required key-value pairs are provided according to the selected data type.
- Verify network connectivity and endpoint accessibility.
- Use the correct data type matching the API expectations.