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: "Query" (query parameters) or "JSON" (JSON body). |
| Query Parameters | When "Type of Data" is set to "Query", specify one or more key-value pairs as query parameters to include in the URL. |
| JSON Object | When "Type of Data" is set to "JSON", specify one or more 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. The structure typically reflects the HTTP response returned by HttpBin, including details about the request made (such as headers, args/query parameters, and JSON data sent).
If the response includes 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.
- 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: Request fails or times out.
- Cause: Network issues or HttpBin service downtime.
- Resolution: Check internet connection and HttpBin status.
Issue: Unexpected response or error from HttpBin.
- Cause: Incorrectly formatted query parameters or JSON body.
- Resolution: Verify that keys and values are correctly specified and match expected API input.
Issue: No output or empty response.
- Cause: Possibly no data sent or incorrect property selection.
- Resolution: Ensure "Type of Data" matches the provided input fields and that at least one key-value pair is defined.