Overview
This node interacts with the HttpBin API to perform HTTP DELETE requests. It allows users to send data either as query parameters or as a JSON body in the DELETE request. This is useful for testing and debugging HTTP DELETE operations, simulating API calls that require deletion of resources with optional parameters.
Common scenarios include:
- Testing REST APIs that use DELETE methods with query parameters.
- Sending JSON payloads in DELETE requests where the API expects a body.
- Debugging how an API handles different types of input data on DELETE endpoints.
Example: Deleting a resource identified by query parameters or sending additional JSON data to specify deletion criteria.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Select the type of data to send with the DELETE request. Options: Query (query parameters), JSON (JSON body). |
| Query Parameters | Key-value pairs representing the query parameters to include in the URL when Type of Data is set to Query. Each pair consists of a key and its corresponding value. |
| JSON Object | Key-value pairs representing the JSON properties to include in the request body when Type of Data is set to JSON. Each pair consists of a key and its corresponding value. |
Output
The node outputs JSON data returned from the HttpBin API after performing the DELETE request. The output JSON typically contains details about the request made, such as the URL, headers, query parameters, and JSON body received by HttpBin, which helps verify what was sent.
If the API returns binary data (not typical for HttpBin DELETE), it would be included in the binary output field, 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 by default.
- No other external dependencies are needed.
Troubleshooting
- Incorrect query parameters or JSON body: Ensure keys and values are correctly specified; missing or malformed data can cause unexpected API responses.
- Network errors: Verify internet connectivity and that
https://httpbin.orgis reachable. - Unexpected response format: If the API changes or is down, the node may return errors or empty responses.
- Misconfiguration of
Type of Data: Selecting the wrong data type (e.g., JSON when only query parameters are supported) may lead to failed requests or ignored data.