HttpBin icon

HttpBin

Interact with HttpBin API

Actions2

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.

Practical examples include:

  • Deleting a resource identified by query parameters.
  • Sending a JSON payload with delete instructions or filters.
  • Testing how an API handles DELETE requests with different types of input data.

Properties

Name Meaning
Type of Data Selects the format of data sent with the DELETE request: "Query" (query parameters) or "JSON" (JSON body).
Query Parameters Key-value pairs to be sent as URL query parameters when "Type of Data" is set to "Query".
JSON Object Key-value pairs to be sent as JSON properties in the request body when "Type of Data" is set to "JSON".

Output

The node outputs JSON data returned from the HttpBin API after performing the DELETE request. The output contains the response details such as headers, args (query parameters), data (body content), and other metadata reflecting the request made.

If binary data were involved (not applicable here), it would represent file contents or similar, but this node focuses on JSON responses.

Dependencies

  • Requires access to the public HttpBin API at https://httpbin.org.
  • Optionally uses an API key credential if configured, though not mandatory.
  • No additional environment variables are required.

Troubleshooting

  • Common issues:

    • Incorrectly formatted query parameters or JSON body may cause the API to reject the request.
    • Network connectivity problems can prevent reaching the HttpBin service.
    • Selecting the wrong "Type of Data" option might lead to unexpected request formats.
  • Error messages:

    • HTTP errors like 400 Bad Request indicate malformed input; verify keys and values.
    • 404 Not Found suggests incorrect endpoint usage.
    • Timeout or network errors imply connectivity issues.

To resolve these, ensure proper formatting of inputs, verify network access, and confirm correct operation/resource selections.

Links and References

Discussion