HttpBin icon

HttpBin

Interact with HttpBin API

Actions2

Overview

This node interacts with the HttpBin API, specifically performing HTTP DELETE requests. It allows users to send DELETE requests with either query parameters or JSON body data. This is useful for testing and debugging HTTP DELETE operations against APIs that accept such requests.

Common scenarios include:

  • Testing API endpoints that require DELETE requests with specific query parameters.
  • Sending JSON payloads in a DELETE request body to simulate complex delete operations.
  • Debugging how an API handles different types of input data on DELETE calls.

Example: Deleting a resource identified by query parameters or sending a JSON object specifying deletion criteria.

Properties

Name Meaning
Type of Data Select the type of data to send with the DELETE request. Options: Query (query parameters), JSON (JSON body).
Query Parameters When "Type of Data" is Query, specify one or more key-value pairs as query parameters to be sent with the DELETE request.
JSON Object When "Type of Data" is JSON, specify one or more key-value pairs as JSON properties to be included in the DELETE request body.

Output

The node outputs the response from the HttpBin API in the json field. The structure corresponds to the HTTP response returned by HttpBin for the DELETE request made, typically including details about the request received by HttpBin (such as headers, args, data, json, etc.).

No binary data output is indicated.

Dependencies

  • Requires access to the public HttpBin API at https://httpbin.org.
  • Optionally uses an API authentication token if configured, but it is not required.
  • No other external dependencies are needed.

Troubleshooting

  • Issue: Incorrect or missing query parameters or JSON body keys may cause unexpected responses.
    • Resolution: Ensure all required keys and values are correctly set according to the target API's expectations.
  • Issue: Network errors or inability to reach https://httpbin.org.
    • Resolution: Check internet connectivity and firewall settings.
  • Issue: Unexpected response format.
    • Resolution: Verify that the "Type of Data" matches the expected input type for the API endpoint.

Links and References

Discussion