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 include in the URL. Each pair consists of a Key (string) and a Value (string). |
| JSON Object | When "Type of Data" is set to JSON, this property lets you specify multiple key-value pairs as JSON properties to include in the request body. Each pair consists of a Key (string) and a Value (string). |
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), and data (body content).
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 an optional API authentication token can be configured if needed.
- The node uses standard HTTP headers including
Accept: application/jsonandContent-Type: application/json.
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.
- Using unsupported keys or values might result in the API ignoring them or returning errors.
Error messages:
- HTTP errors (e.g., 4xx or 5xx status codes) indicate problems with the request or server.
- JSON parsing errors may occur if the input data is malformed.
Resolutions:
- Verify the format and correctness of query parameters or JSON body fields.
- Ensure network connectivity to https://httpbin.org.
- Check that the selected "Type of Data" matches the provided input fields.