Differences

This shows you the differences between two versions of the page.

--- api [2023/11/26 11:58]
kaduuwikiadmin
+++ api [2025/03/26 08:50] (current)
kaduuwikiadmin [API Script to find and extracts accounts in leaks]
@@ Line 12: / Line 12: @@
 ===== API Documentation =====
-Please find the API documentation here {{ ::kaduu-2.2-swagger_3_.zip |}}. The{{ :kaduu-2.0.pdf | PDF documentation has}} some more details about authentication and filters.
+Please find two API documentations here:
+  * {{ ::kaduu-2.2-swagger-fixed.zip |}}
+  * The{{ :kaduu-2.0.pdf | PDF documentation has}} some more details about authentication and filters.
 Please note that Kaduu SaaS API is based on a REST/HTTPS protocol with JSON format. All endpoints except the
@@ Line 53: / Line 55: @@
-===== API Script =====
+===== API Script to extract leaks and save it to a CSV =====
-The customer has various options in Kaduu for accessing the query data:
+{{ ::query_leaks.zip |The Leak Center Query Tool}} is a Python script that interacts with the Leak Center API to fetch and process leaked data. It supports authentication using credentials provided interactively or through an optional auth.txt file, which must be formatted as username,password. The script queries for a target domain, which can be supplied interactively or via an input.txt file. Optionally, a date range can be specified through a DateRange.txt file or interactively; if skipped, no date filter is applied. The script normalizes different date formats, such as yyyy.mm.dd, yy.mm.dd, or yyyy-mm-dd, into a format compatible with the backend.
-  * Via dashboard: data can be displayed and then exported (CSV, XML, DOCX etc)
-  * Via webhook
-  * Via REST API
-  * Via alerting (email)
-The REST API allows you great flexibility in automation and integration into your existing processes and applications. In this chapter we illustrate how the API can be used with a customizable Python script which could assist you with few business use cases:
-  * White labeled alerts: You use Kaduu to regularly provide end customers or specific people with email alerts on certain topics (e.g. leaked data). To do this, you want to use an email with your design, company name and structure and also send this via your infrastructure.
-  * Ticketing System Integration: You want to integrate Kaduu into your existing environment and create tickets or incidents automatically in Splunk, Jira, Slack or similar systems.
-  * Automated Output Parsing: You want to store all results for certain search queries daily in an easy-to-process format (CSV, XLS, etc.) locally in a folder of your choice for analysis and further processing.
-  * Reduce Workload in Alerting: You want to save time when using Kaduu's email alerts: Instead of logging into the system for email alerts and researching the cause of the alerts, you want to receive the specific raw data of the alerts via email.
+The script processes paginated responses from the API and writes the results to a CSV file, Leaks.csv, with structured headers including id, createdAt, content, fileName, and more.
+===== API Script to find and extracts accounts in leaks =====
+This script is designed to help users search through data leaks for specific information like email addresses and passwords. It automates the process of logging into the Leak Center's API service, where the leaks are stored. Once logged in, the script uses search criteria specified by the user (such as particular tags that might relate to the type of information they're interested in, e.g., "accounts") to find relevant data within the leaks. Please check the readme inside the script for more details. {{ :leakapi_v2.zip |Download the file here.}}

My DokuWiki

User Tools

Site Tools

Differences

Page Tools