Add dehashed API for breaches #75
Description
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:
nameemailusernameip_addresspasswordhashed_passwordvinlicense_plateaddressphonesocialcryptocurrency_addressdomain
Requested Functionality
- Add a client or module to query the DeHashed
/searchendpoint - 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.