Overview
This node allows users to perform 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 an API endpoint. This functionality is useful in scenarios where you need to delete resources on a remote server and the API requires specific parameters either as URL query strings or within the request body.
Practical examples include:
- Deleting a user or item by specifying identifiers as query parameters.
- Sending a JSON payload to specify complex deletion criteria or filters.
Properties
| Name | Meaning |
|---|---|
| Type of Data | Selects the format of data sent with the DELETE request. Options: "Query" (query parameters) or "JSON" (JSON body). |
| Query Parameters | When "Type of Data" is set to "Query", this property lets you define multiple key-value pairs to be sent as URL query parameters. Each pair consists of a key and its corresponding value. |
| JSON Object | When "Type of Data" is set to "JSON", this property lets you define multiple key-value pairs to be sent as JSON properties in the request body. Each pair consists of a key and its corresponding value. |
Output
The node outputs the response from the HTTP DELETE request in the json field of the output data. The structure of this JSON depends on the API's response but typically contains confirmation of deletion or error details.
If the API returns binary data (uncommon for DELETE), it would be available in the binary output, but this node primarily handles JSON responses.
Dependencies
- Requires an API authentication token credential to authorize requests.
- The base URL for requests is preset to
https://oura.org. - The node expects the API to accept and respond with JSON content type.
Troubleshooting
- Incorrect parameter placement: Ensure that when "Type of Data" is set to "Query," all parameters are correctly defined as query parameters; similarly, use JSON properties only when "Type of Data" is "JSON."
- Authentication errors: Verify that the API authentication token is valid and properly configured.
- API endpoint issues: Confirm the target URL and resource exist and support DELETE operations.
- Empty or malformed parameters: Make sure keys and values are correctly specified; missing keys or empty values may cause request failures.
- Unexpected response formats: If the API returns non-JSON responses, the node might not handle them correctly.
Links and References
- HTTP DELETE Method - MDN Web Docs
- Oura API Documentation (for understanding the API endpoints and expected parameters)