Overview
This node allows performing HTTP DELETE requests with flexible data input options. It is designed to send either query parameters or JSON body data when making a DELETE request to a specified endpoint. This functionality is useful in scenarios where you need to delete resources on a remote server and the API expects additional data either as URL query parameters or as a JSON payload.
Practical examples include:
- Deleting a user by sending their ID as a query parameter.
- Removing an item from a database by passing JSON data describing the item to delete.
- Interacting with RESTful APIs that require specific data formats for DELETE operations.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the format of data sent with the DELETE request. Options: Query (query parameters), JSON (JSON body). |
| Query Parameters | Key-value pairs representing the query parameters to append to the URL when Type of Data is set to Query. Each pair consists of a key and its corresponding value. |
| JSON Object | Key-value pairs representing the JSON properties to include in the request body when Type of Data is set to JSON. Each pair consists of a key and its corresponding value. |
Output
The node outputs JSON data representing the response received from the HTTP DELETE request. The structure of this JSON depends on the external API's response but typically includes status information, confirmation of deletion, or error messages.
If the API returns binary data (not indicated here), it would be accessible via the node's binary output field, but this node primarily handles JSON responses.
Dependencies
- Requires access to an HTTP endpoint that supports DELETE requests.
- Optionally requires an API authentication token or key if the target API is secured (the node supports credentials configuration).
- No other external dependencies are indicated.
Troubleshooting
Common Issues:
- Incorrectly formatted query parameters or JSON body may cause the API to reject the request.
- Missing required authentication tokens can lead to authorization errors.
- Network connectivity issues will prevent the request from completing.
Common Error Messages:
- 400 Bad Request: Usually caused by invalid query parameters or JSON body content. Verify keys and values.
- 401 Unauthorized / 403 Forbidden: Indicates missing or invalid authentication credentials. Ensure proper API key/token is configured.
- 404 Not Found: The requested resource does not exist at the given endpoint or with the provided identifiers.
- 500 Internal Server Error: Server-side issue; retry later or check API status.
To resolve these errors, verify the correctness of input properties, ensure valid credentials are supplied, and confirm the API endpoint URL.
Links and References
- HTTP DELETE Method - MDN Web Docs
- REST API Design - Best Practices
- HttpBin - HTTP Request & Response Service (for testing HTTP requests)