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 JSON body data. This is useful for testing and debugging HTTP DELETE operations, simulating how an API endpoint would handle such requests.
Common scenarios include:
- Testing RESTful APIs that require DELETE requests with specific query parameters.
- Sending JSON payloads in a DELETE request body to simulate complex delete operations.
- Debugging and inspecting server responses to DELETE requests.
Example: Deleting a resource identified by query parameters or sending a JSON object specifying 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 | When "Type of Data" is set to Query, specify key-value pairs as query parameters appended to the URL. |
| JSON Object | When "Type of Data" is set to JSON, specify key-value pairs as properties in the JSON body of the request. |
Output
The node outputs the response from the HttpBin API in the json field. This typically includes details about the received request such as headers, args (query parameters), and data (body content). The output structure reflects the HttpBin service's echo of the DELETE request, useful for verifying what was sent.
No binary data output is produced by this node.
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 is necessary.
Troubleshooting
Issue: Empty or missing query parameters or JSON body in the request.
- Cause: Incorrect configuration of the "Type of Data" property or missing key-value pairs.
- Solution: Ensure the correct "Type of Data" is selected and that key-value pairs are properly defined.
Issue: Unexpected response or errors from HttpBin.
- Cause: Network issues or invalid request formatting.
- Solution: Verify network connectivity and review the input properties for correctness.
Error Message: HTTP error codes returned by HttpBin (e.g., 400 Bad Request).
- Resolution: Check that query parameters or JSON body conform to expected formats and that keys/values are valid strings.