---
title: "Get leak information by ID"
method: POST
path: "/v1/leaks/info"
tags: ["leaks"]
---

# Get leak information by ID

`POST /v1/leaks/info`

Retrieve detailed leak information by leak ID. Passwords are unmasked after domain verification. See [Domain Verification](/cloud/credential-monitoring#domain-verification) for setup instructions.

## Request body

- object
  - `leakid` string, required — 32-character MD5 hash identifying the leak

## Response `200`

Leak information retrieved successfully

- object
  - `success` boolean
  - `data` object
    - `id` string
    - `url` string
    - `username` string
    - `password` string
    - `device_ip` string
    - `hostname` string
    - `os` string
    - `malware_path` string
    - `country` string
    - `log_date` string
    - `hardware_id` string
    - `domain` string — Domain this leak is associated with - used for filtering
    - `email_domain` string — Domain extracted from email addresses
    - `fetched_at` string
    - `status` string

## Other responses

- `400` — Bad request - Invalid leak ID format or missing leak ID
- `401` — Example response
- `403` — Access denied - Insufficient permissions to access this leak
- `404` — Leak not found
- `500` — Example response
- `default` — Example response

## Changes

> 22 revisions in range; 1 could not be searched.

- **2025-10-28** `c9df54e2fb2c` — 1 info
  - endpoint added
- **2023-12-05** `5c3748c387f7` — 1 breaking
  - api path removed without deprecation

[Change history](https://skmtc.dev/projectdiscovery/apis/pdcp-api/changes/v1/leaks/info/post.md)

---

[API](https://skmtc.dev/projectdiscovery/apis/pdcp-api.md) · [All operations](https://skmtc.dev/projectdiscovery/apis/pdcp-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/projectdiscovery/pdcp-api/revisions/220f0adf9efd/schema)