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. Typical use cases include simulating API DELETE calls, validating server responses to DELETE requests, or experimenting with different payload formats.
For example, a user might want to delete a resource identified by query parameters or send a JSON body with specific instructions for deletion. This node facilitates both approaches.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the format of data sent 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 allows specifying multiple key-value pairs as query parameters 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 allows specifying multiple key-value pairs that form the JSON body of the DELETE request. Each pair consists of a Key (property name) and Value (property value). |
Output
The node outputs the response from the HttpBin API in JSON format under the json output field. This typically includes details about the received request such as headers, args (query parameters), and data (body content), reflecting what was sent. The output helps verify that the DELETE request was constructed and sent correctly.
No binary data output is produced by this node.
Dependencies
- Requires access to the public HttpBin API at
https://httpbin.org. - No mandatory authentication is required, but an optional API key credential can be configured.
- Network connectivity to the HttpBin service is necessary.
Troubleshooting
Common issues:
- Incorrectly formatted query parameters or JSON body may cause unexpected responses.
- Network errors if the HttpBin service is unreachable.
- Misconfiguration of the "Type of Data" property leading to sending data in an unintended format.
Error messages:
- HTTP errors returned by HttpBin (e.g., 400 Bad Request) usually indicate malformed input; verify keys and values.
- Timeout or network errors suggest connectivity problems; check internet connection and proxy settings if applicable.