Overview
This node interacts with the HttpBin API, specifically allowing users 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 body. Practical applications include simulating API DELETE calls, validating server responses to DELETE requests, or experimenting with different payload formats (query vs JSON) without needing a real backend.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the format of data sent with the DELETE request: "Query" (query parameters) or "JSON" (JSON body). |
| Query Parameters | Key-value pairs representing the query parameters to be appended to the URL when "Type of Data" is set to "Query". |
| JSON Object | Key-value pairs representing the JSON properties to be sent in the request body when "Type of Data" is set to "JSON". |
Output
The node outputs JSON data returned from the HttpBin API after performing the DELETE request. The output JSON reflects the request details as interpreted by HttpBin, including any query parameters or JSON body sent. This allows users to verify what was received by the server. There is no binary data output.
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
- Common issues:
- Incorrectly formatted query parameters or JSON body may cause unexpected responses.
- Network errors if the HttpBin service is unreachable.
- Error messages:
- HTTP errors (e.g., 4xx or 5xx) indicate issues with the request or server; verify the request format and network status.
- Missing or invalid input properties will prevent the request from being formed correctly; ensure all required fields are filled.