Overview
This node interacts with the HttpBin API, specifically allowing users to perform HTTP DELETE requests. It is useful for testing and debugging HTTP DELETE operations by sending either query parameters or JSON data in the request. Practical applications include simulating API DELETE calls, validating server responses to DELETE requests, or experimenting with different payload formats (query vs JSON) without needing a real backend.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the format of data sent with the DELETE request: either as Query Parameters or JSON Body. Options: "Query", "JSON". |
| Query Parameters | When "Type of Data" is set to Query, this property allows specifying multiple key-value pairs to be sent as URL query parameters. Each pair consists of a Key and its corresponding Value. |
| JSON Object | When "Type of Data" is set to JSON, this property allows specifying multiple 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 the response from the HttpBin API in JSON format under the json field. This typically includes details about the received request such as headers, args (query parameters), and data (body content). The output helps verify what was sent and how the server interpreted the DELETE request.
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 key credential can be configured if needed.
- Network connectivity to the HttpBin service is necessary.
Troubleshooting
- Common issues:
- Incorrectly formatted query parameters or JSON body may cause unexpected responses.
- Network errors or inability to reach https://httpbin.org will result in request failures.
- Error messages:
- HTTP errors (e.g., 4xx or 5xx status codes) indicate issues with the request or server.
- JSON parsing errors may occur if the response is not valid JSON.
- Resolutions:
- Verify that keys and values in query parameters or JSON body are correctly specified.
- Ensure network connectivity and that the HttpBin service is reachable.
- Check that the selected "Type of Data" matches the provided input fields.