Overview
This node interacts with the HttpBin API, specifically performing HTTP DELETE requests. It allows users to send DELETE requests with either query parameters or a JSON body payload. This is useful for testing and debugging HTTP DELETE operations against APIs that accept such requests.
Common scenarios include:
- Testing API endpoints that require DELETE requests with specific query parameters.
- Sending JSON data in the body of a DELETE request to simulate real-world API interactions.
- Debugging how an API handles different types of DELETE request payloads.
For example, you might use this node to delete a resource identified by query parameters or to send a JSON object specifying deletion criteria.
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, specify one or more key-value pairs as query parameters to be appended to the URL. |
| JSON Object | When "Type of Data" is set to JSON, specify one or more key-value pairs to be sent as a JSON body in the DELETE request. |
Output
The node outputs the response from the HttpBin API in the json field of the output data. This typically includes details about the request received by HttpBin, such as the URL, headers, query parameters, and body content, allowing you to verify what was sent.
If the API returns binary data (not typical for HttpBin DELETE), it would be available in the binary output, but this node primarily deals with JSON responses.
Dependencies
- Requires access to the public HttpBin API at https://httpbin.org.
- Optionally uses an API authentication token if configured, but HttpBin does not require authentication for basic usage.
- No additional environment variables or credentials are strictly necessary.
Troubleshooting
Issue: The DELETE request returns unexpected results or errors.
- Cause: Incorrectly formatted query parameters or JSON body.
- Solution: Verify that keys and values are correctly specified and match the expected API format.
Issue: Network errors or timeouts.
- Cause: Connectivity issues or HttpBin service downtime.
- Solution: Check network connection and retry later.
Issue: Response does not reflect sent data.
- Cause: Mismatch between selected "Type of Data" and provided input fields.
- Solution: Ensure that when "Query" is selected, only query parameters are provided; when "JSON" is selected, provide JSON body properties.