GET /v1/buckets lists the twelve main ones, each with the value to send and a readable label. It needs no key and takes no request. Use it to fill a bucket picker for Storage ID Search, or to put a label on the bucket of a record.
When to use it
- You build a bucket picker for Storage ID Search.
- You show a readable name for the
bucketof an Intelligence Search or Identity Portal record. - You group or filter records by where they come from.
Request
GET /v1/buckets. No parameters, no body, no key.
What you get back
The example is trimmed: the real list holds the twelve buckets below.
The twelve buckets, in the order the list gives them:
More precise buckets
A record can name a more precise bucket than the twelve, such asleaks.private.comb, web.public.gov or dumpster.web.1. Storage ID Search takes it as it is. A bucket is lowercase letters and digits, in up to five parts separated by dots, 100 characters at most.
Cost and limits
- Free: no key, no credits, nothing taken from your daily quota.
- Per address: it counts in the 120 calls a minute allowed from one address. Over that,
429 ip_rate_limited: waitRetry-Afterseconds. - Browsers: call it from your server or a script. Web pages on other sites cannot call the API directly.
Errors
Errors use the usual envelope:
{ "error": { "code": "…", "message": "…" } }.
Tips
- Cache it. The list rarely changes. Fetch it once and keep it, rather than before every search.
- Send the value, show the label.
leaks.logsgoes in the request;Leaks » Logsis for people. - Do not check a record’s bucket against the twelve. A precise bucket such as
leaks.private.combis valid. Show a value you do not know as it is. - The bucket is where, not what. It tells where a record is stored. The kind of file is a separate matter: Intelligence Search filters on it with
media_type.
Reference
List buckets
The response schema, and a playground to try it.

