Kaduu Leaks icon

Kaduu Leaks

Interact with Kaduu Leaks API

Actions3

Leak → Get

AI-generated

Overview

The node interacts with the Kaduu Leaks API to retrieve information about data leaks. Specifically, for the "Leak" resource and the "Get" operation, it fetches detailed information about a single leak identified by its unique Leak ID.

This node is useful in scenarios where you want to programmatically access specific leak details from the Kaduu Leaks database, such as integrating leak data into security dashboards, alerting systems, or compliance tools.

Example use case:
You have an automated workflow that monitors suspicious activity related to leaked credentials. When a particular leak ID is detected, this node can fetch detailed information about that leak to enrich your incident reports or trigger further investigation steps.

Properties

Name Meaning
Leak ID The unique identifier of the leak to retrieve. This is a required string input.

Output

The output JSON contains the detailed information of the requested leak. The structure corresponds directly to the leak object returned by the Kaduu Leaks API for the specified Leak ID.

  • If the response includes multiple leaks (not typical for "get"), each leak is wrapped in an item with additional metadata fields:

    • totalElements: total number of leaks available
    • totalPages: total pages of results
    • currentPage: current page number
    • pageSize: number of items per page

  • For the "get" operation, the output will be a single JSON object representing the leak's data.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Kaduu Leaks API.
  • The base URL used for requests is https://app.leak.center/svc-saas.
  • The node uses HTTP GET requests to interact with the API endpoints.
  • Timeout for API requests is set to 10 seconds.

Troubleshooting

  • Missing Leak ID error:
    If the Leak ID property is empty or missing, the node throws an error indicating that the Leak ID is required. Ensure you provide a valid Leak ID string.

  • API request failures:
    Errors from the API (e.g., network issues, invalid credentials, or non-existent Leak ID) are caught and reported as node errors. Verify your API key credential and the Leak ID correctness.

  • No valid response data received:
    If the API returns no data or an unexpected response, the node throws an error. Check the API status and ensure the Leak ID exists.

  • Search query length validation (not applicable here but relevant for other operations):
    For search operations, queries must be between 3 and 10,000 characters; otherwise, an error is thrown.

Links and References

Discussion