Overview
This node interacts with the HttpBin API, specifically performing HTTP DELETE requests when the "HTTP Verb" resource and "DELETE" operation are selected. It allows users to send DELETE requests with either query parameters or JSON body data. This is useful for testing APIs that support DELETE methods, debugging HTTP clients, or automating workflows that require deleting resources on remote servers.
Practical examples include:
- Sending a DELETE request to remove a resource identified by query parameters.
- Testing how an API handles DELETE requests with JSON payloads.
- Automating cleanup tasks in web services that accept DELETE operations.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Select the type of data to send with the DELETE request. Options: Query (query parameters) or JSON (JSON body). |
| Query Parameters | Key-value pairs representing the query parameters to include in the DELETE request URL. |
| JSON Object | Key-value pairs representing the JSON properties to include in the DELETE request body. |
Details:
- Type of Data: Determines whether the data is sent as URL query parameters or as a JSON body.
- Query Parameters: When "Query" is selected, users can specify multiple key-value pairs to be appended to the request URL.
- JSON Object: When "JSON" is selected, users can specify multiple key-value pairs to be included in the request body as JSON.
Output
The node outputs the response from the HttpBin API in the json field of the output data. The structure typically reflects the HTTP response returned by HttpBin, including details such as the URL requested, headers, args (query parameters), and data (body content).
If the response includes binary data, it would be handled accordingly, but based on this operation (DELETE with JSON or query parameters), the output is primarily JSON-formatted response data describing the request received by HttpBin.
Dependencies
- Requires access to the public HttpBin API at
https://httpbin.org. - Optionally uses an API authentication token if configured, but it is not mandatory.
- No other external dependencies are required.
Troubleshooting
Common Issues:
- Incorrectly formatted query parameters or JSON body may cause the API to reject the request or return unexpected results.
- Network connectivity issues can prevent reaching the HttpBin service.
- Selecting the wrong "Type of Data" option may lead to sending data in an unintended format.
Error Messages:
- HTTP errors (e.g., 400 Bad Request) usually indicate malformed input; verify keys and values.
- Timeout or network errors suggest connectivity problems; check internet connection and firewall settings.