Overview
This node interacts with the HttpBin API to perform HTTP DELETE requests. It allows users to send data either as query parameters or as a JSON body in the DELETE request. This is useful for testing and debugging HTTP DELETE operations, simulating API calls that require deletion of resources with optional parameters.
Common scenarios include:
- Testing REST APIs that use DELETE methods with query parameters.
- Sending JSON payloads in DELETE requests where the API expects a body.
- Debugging how an API handles different types of input data on DELETE endpoints.
Example: Deleting a resource identified by query parameters or sending metadata in the JSON body to specify what should be deleted.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Select whether to send data as Query Parameters (queryParameter) or as JSON Body (jsonData). |
| Query Parameters | Key-value pairs representing the query parameters to append to the DELETE request URL. |
| JSON Object | Key-value pairs representing the JSON properties to include in the DELETE request body. |
Output
The node outputs the response from the HttpBin API in the json field. This typically includes details about the received request such as headers, args (query parameters), and data (body content). The output structure reflects the HttpBin service's echo of the request, useful for verifying 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 key credential if configured, but it is not mandatory.
- No additional environment variables or special n8n configurations are required.
Troubleshooting
- Issue: Incorrect or missing query parameters or JSON body fields may cause unexpected responses.
- Resolution: Ensure keys and values are correctly set in the node’s properties according to the API expectations.
- Issue: Network errors or inability to reach
https://httpbin.org.- Resolution: Check internet connectivity and firewall settings.
- Error: Invalid JSON body format.
- Resolution: Verify that JSON data is properly structured and all required keys are provided.
- Error: Unexpected HTTP status codes.
- Resolution: Review the API documentation for expected behavior and adjust parameters accordingly.