Overview
This node interacts with the HttpBin API, specifically performing HTTP DELETE requests. It allows users to send either query parameters or JSON data in the DELETE request. This is useful for testing and debugging HTTP DELETE operations against an API endpoint, simulating how a server would handle such requests.
Practical examples include:
- Deleting resources on a test server by sending specific query parameters.
- Sending JSON payloads in a DELETE request to APIs that accept body content with DELETE methods.
- Debugging and inspecting how different types of data are handled in DELETE requests.
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 to be 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 to be sent in the request body. Each pair consists of a Key (string) and a Value (string). |
Output
The node outputs JSON data representing the response from the HttpBin API after performing the DELETE request. The structure typically includes details about the request received by HttpBin, such as headers, args (query parameters), and data (body content), allowing inspection of what was sent.
No binary data output is produced by this node.
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.
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 can prevent reaching the HttpBin service.
- Using JSON body with DELETE requests might not be supported by all servers; ensure the target API supports it.
Error messages:
- HTTP errors (e.g., 4xx or 5xx status codes) indicate issues with the request or server.
- Timeout or network errors suggest connectivity problems.
Resolutions:
- Verify the correctness of keys and values in query parameters or JSON body.
- Check network connection and proxy settings.
- Confirm that the API endpoint supports DELETE requests with the chosen data type.