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 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 and its corresponding 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 and its corresponding Value. |
Output
The node outputs JSON data representing the response from the HttpBin API after performing the DELETE request. The structure typically includes details about the request received by HttpBin, such as headers, args (query parameters), and JSON body content, reflecting what was sent. There is no binary output.
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 must be available.
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) indicate issues with the request or server.
- Validation errors if required keys or values are missing in the input properties.
- Resolutions:
- Ensure all required keys and values are provided and correctly typed.
- Verify network connectivity and that the HttpBin service is reachable.
- Use the correct "Type of Data" option matching the intended payload format.