[GH-ISSUE #75] Add dehashed API for breaches #3602

New Issue

2026-07-12T09:10:25-05:00

GiteaMirror commented

2026-07-12 09:10:25 -05:00

Originally created by @xhzeem on GitHub (Nov 20, 2025).
Original GitHub issue: https://github.com/reconurge/flowsint/issues/75

Please consider adding support for querying the DeHashed API. This would allow retrieval of breach-related fields directly from the /search endpoint.

API Example

url -X POST 'https://api.dehashed.com/v2/search' \
  --header 'Dehashed-Api-Key: secret_api_key==' \
  --header 'Content-Type: application/json' \
  --data-raw '{"query": "domain:exmaple.com"}'

Example Response

{
    "balance": 100,
    "entries": [
        {
            "id": "5603802198", 
            "email": ["test@example.com"],
            "ip_address": ["127.0.0.1"],
            "username": ["username@example.com"], 
            "password": ["examplepassword"],
            "hashed_password": ["password:salt||passwordhash"],
            "name": ["name"],
            "dob": ["01/02/60"],
            "license_plate": ["123456"],
            "address": ["example address"],
            "phone": ["+18005551234"],
            "company": ["example company"],
            "url": ["url.com"],
            "social": ["social username"],
            "cryptocurrency_address": ["0xcryptocurrencyaddress"],
            "database_name": "Example Database Name",
            "raw_record": {
                "le_only": true,
                "unstructured": true
            }
        }
    ],
    "took": "179µs",
    "total": 5
}

Supported Fields
The API returns the following fields, which would ideally be mapped in the integration:

name
email
username
ip_address
password
hashed_password
vin
license_plate
address
phone
social
cryptocurrency_address
domain

Requested Functionality

Add a client or module to query the DeHashed /search endpoint
Support for the fields listed above
Authentication handling (username/API key + password)
Basic error handling for empty or invalid responses

Let me know if you'd like this adapted to a specific issue template.

Originally created by @xhzeem on GitHub (Nov 20, 2025). Original GitHub issue: https://github.com/reconurge/flowsint/issues/75 Please consider adding support for querying the DeHashed API. This would allow retrieval of breach-related fields directly from the `/search` endpoint. **API Example** ```bash url -X POST 'https://api.dehashed.com/v2/search' \ --header 'Dehashed-Api-Key: secret_api_key==' \ --header 'Content-Type: application/json' \ --data-raw '{"query": "domain:exmaple.com"}' ``` **Example Response** ```json { "balance": 100, "entries": [ { "id": "5603802198", "email": ["test@example.com"], "ip_address": ["127.0.0.1"], "username": ["username@example.com"], "password": ["examplepassword"], "hashed_password": ["password:salt||passwordhash"], "name": ["name"], "dob": ["01/02/60"], "license_plate": ["123456"], "address": ["example address"], "phone": ["+18005551234"], "company": ["example company"], "url": ["url.com"], "social": ["social username"], "cryptocurrency_address": ["0xcryptocurrencyaddress"], "database_name": "Example Database Name", "raw_record": { "le_only": true, "unstructured": true } } ], "took": "179µs", "total": 5 } ``` **Supported Fields** The API returns the following fields, which would ideally be mapped in the integration: * `name` * `email` * `username` * `ip_address` * `password` * `hashed_password` * `vin` * `license_plate` * `address` * `phone` * `social` * `cryptocurrency_address` * `domain` **Requested Functionality** * Add a client or module to query the DeHashed `/search` endpoint * Support for the fields listed above * Authentication handling (username/API key + password) * Basic error handling for empty or invalid responses Let me know if you'd like this adapted to a specific issue template.

GiteaMirror added the enhancement label 2026-07-12 09:10:25 -05:00

GiteaMirror closed this issue

2026-07-12 09:10:26 -05:00

GiteaMirror commented

2026-07-12 09:10:26 -05:00

@z3rodaycve commented on GitHub (May 12, 2026):

hello @xhzeem, I believe this issue can be closed as it was implemented in #138.

@z3rodaycve commented on GitHub (May 12, 2026): hello @xhzeem, I believe this issue can be closed as it was implemented in #138.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/flowsint#3602