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 against an API endpoint, simulating how a server would respond to such requests.
Practical examples include:
- Deleting resources identified by query parameters.
- Sending structured JSON data in the body of a DELETE request to APIs that accept payloads on DELETE.
- Testing API endpoints during development without needing a full backend setup.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Select the type of data to send with the DELETE request: either Query Parameters or JSON Body. Options: "Query", "JSON". |
| Query Parameters | When "Type of Data" is set to Query, specify one or more key-value pairs as query parameters appended to the URL. Each pair consists of a Key (string) and a Value (string). |
| JSON Object | When "Type of Data" is set to JSON, specify one or more key-value pairs as JSON properties sent in the request body. Each pair consists of a Key (string) and a Value (string). |
Output
The node outputs the response from the HttpBin API in the json field. The structure typically reflects the HTTP response details returned by HttpBin, including the data sent, headers, and other metadata about the DELETE request.
No binary data output is indicated.
Dependencies
- Requires access to the public HttpBin API at https://httpbin.org.
- Optionally uses an API authentication credential if configured, but it is not mandatory.
- No additional environment variables or external services are required beyond internet access.
Troubleshooting
Common issues:
- Incorrectly formatted query parameters or JSON body may cause the API to reject the request or return unexpected results.
- Network connectivity problems will prevent reaching the HttpBin service.
- Using JSON body with APIs that do not support it on DELETE may lead to errors or ignored payloads.
Error messages:
- HTTP error responses from HttpBin (e.g., 4xx or 5xx status codes) indicate client or server errors; verify the request format and endpoint.
- Timeout or network errors suggest connectivity issues; check internet connection and proxy settings if applicable.