Overview
This node interacts with the HttpBin API, specifically allowing you to perform HTTP DELETE requests with customizable data payloads. It is useful for testing and debugging HTTP DELETE operations by sending either query parameters or JSON body data to the endpoint. Practical examples include deleting resources identified by query parameters or sending structured JSON data in the request body to simulate API delete calls.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Select the type of data to send with the DELETE request: either Query Parameters or JSON Body. |
| Query Parameters | When "Type of Data" is set to Query Parameters, specify one or more key-value pairs to be sent as URL query parameters. Each pair consists of a Key (parameter name) and Value (parameter value). |
| JSON Object | When "Type of Data" is set to JSON Body, specify one or more key-value pairs to be sent as JSON properties in the request body. Each pair consists of a Key (property name) and Value (property value). |
Output
The node outputs JSON data representing the response from the HttpBin API after performing the DELETE request. The json output field contains the parsed response body, which typically includes details about the request received by HttpBin, such as headers, args (query parameters), and data (body content). This allows users to verify what was sent and how the server interpreted it.
No binary data output is produced by this node.
Dependencies
- Requires access to the public HttpBin API at https://httpbin.org.
- No special authentication is 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 or errors.
- Network connectivity problems will prevent the node from reaching the HttpBin API.
- Selecting the wrong "Type of Data" option may lead to data being sent in an unintended format.
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 are correctly specified and match expected API requirements.
- Ensure network access to https://httpbin.org.
- Use the correct "Type of Data" setting matching your intended payload format.