Search Stealer Records with JSON Filter
Same response and flat query parameters as GET /service/v2/stealer/search,
but sends filter or filter_id in a JSON body.
Use POST for the same flows as the web app: AI filters, advanced manual
filters, saved filter contexts, or long filter trees. Keep regular search
controls such as q, cursor, page_size, sort, from, to, view,
and search_id in the query string.
Supports the same basic and advanced stealer filter fields documented on
GET /service/v2/stealer/search.
Authorizations
API key for authentication (lowercase header name)
Query Parameters
Cursor token from the previous response's next_cursor.
Number of results to return.
1 <= x <= 200indexed_at, pwned_at Response field whitelist.
Search session ID from POST /service/search/init.
enriched Body
JSON body used by POST variants of V2 search endpoints.
Use this body when the request has an AI/manual structured filter or an
existing filter context ID. Regular controls such as q, cursor,
page_size, sort, date range, view, and search_id stay in the
query string so GET and POST responses remain identical.
Inline structured filter tree. The tree can contain leaf rules with
field, operator, and value, or compound and / or groups.
When both filter and filter_id are sent, the inline filter is the
explicit filter for this request.
- Option 1
- Option 2
- Option 3
Transient filter context ID returned by POST /service/v2/ai/filter
or by a previous V2 search response. Use it to run the same saved
filter without resending the full filter tree.
^[0-9a-fA-F]{24}$"0123456789abcdef01234567"