Overview
This node interacts with the HttpBin API, specifically allowing you 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. Common scenarios include simulating API DELETE calls, testing endpoint behavior with different payload types, or experimenting with how a server handles query vs. body data on DELETE requests.
For example, you can use this node to send a DELETE request with specific query parameters to remove resources identified by those parameters, or send a JSON body to specify complex deletion criteria.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the type of data to send with the DELETE request: either Query parameters or JSON body data. 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 (string) and a Value (string). |
| JSON Object | When "Type of Data" is set to JSON, this property allows specifying multiple key-value pairs as JSON properties sent in the request body. Each pair consists of a Key (string) and a Value (string). |
Output
The node outputs the response from the HttpBin API in the json field of the output data. This typically contains the details of the DELETE request as interpreted by HttpBin, including the URL, headers, query parameters, and JSON body received. The output structure reflects the standard HttpBin response format for DELETE requests.
No binary data output is produced by this node.
Dependencies
- Requires access to the public HttpBin API at
https://httpbin.org. - No authentication is required, but an optional API key credential can be configured if needed.
- No additional environment variables or external services are necessary.
Troubleshooting
Common issues:
- Sending query parameters when the server expects JSON body data (or vice versa) may lead to unexpected results.
- Incorrectly formatted keys or values in the input properties might cause the request to fail or behave unexpectedly.
- Network connectivity issues will prevent reaching the HttpBin service.
Error messages:
- HTTP errors returned by HttpBin (e.g., 4xx or 5xx status codes) indicate problems with the request or server.
- Validation errors if required keys or values are missing in the input properties.
Resolutions:
- Verify that the "Type of Data" matches the expected input format for your target API.
- Ensure all required key-value pairs are provided and correctly formatted.
- Check network connectivity and HttpBin service availability.