> ## Documentation Index > Fetch the complete documentation index at: https://docs.oathnet.org/llms.txt > Use this file to discover all available pages before exploring further. # Search Victim Profiles > Search victim summaries keyed by `log_id`. Successful responses use the standard search envelope. The same route also accepts POST when you want to send `filter` or `filter_id` in the JSON request body instead of the query string. Dashboard victim filters: - Identity and contact: `email`, `email_domain`, `username`, `discord_id`, `phone`, `steam_id`, `steam_name`. - Device and network: `ip`, `victim_ip`, `hwid`, `os`, `antivirus`, `infection_path`. - Geography and service: `country`, `city`, `domain`, `subdomain`, `service`, `identity_state`. - Volume and richness: `total_docs_min`, `total_docs_max`, `service_count_min`, `service_count_max`. - Metadata: `log_id`, date range via `from` / `to` and `date_field` (`pwned_at` or `indexed_at`). Structured filters can use the same bare victim field names above. When a filter is built from the full stealer investigation view, namespaced fields such as `victims.country`, `victims.service`, and `victims.total_docs` are projected to `country`, `service`, and `total_docs` for this direct victim search endpoint. ## OpenAPI ````yaml /openapi.yaml get /service/v2/victims/search openapi: 3.1.0 info: title: OathNet Service API version: 2.0.0 description: > # OathNet Service API Documentation Welcome to the OathNet Service API. This API provides breach search, stealer search, victims exploration, file search, exports, bulk search, scanners, and OSINT enrichment. ## Authentication Most `/api/service/*` endpoints require authentication via API key. Include your API key in the `x-api-key` header. ``` x-api-key: YOUR_API_KEY ``` You can obtain an API key from your dashboard at https://oathnet.org/dashboard?tab=account ## Rate Limiting & Quotas - Each request consumes from your daily lookup quota - Quota limits depend on your subscription plan - The `_meta.lookups` object in responses shows remaining daily lookups - Service-specific quotas may apply to certain endpoints ## Search Sessions For optimal quota management, initialize a search session before making service calls: 1. Call `/service/search/init` with your query 2. Use the returned `session.id` as `search_id` in subsequent service calls 3. This groups related lookups and provides better quota tracking ## Structured Filters V2 search endpoints share one structured filter contract: - use `GET` for simple searches and URL-friendly flat filters - use `POST` on the same search route when you have an AI/manual structured filter, a saved `filter_id`, or a filter tree that is awkward to URL-encode - `filter` is a JSON-encoded filter tree on query-string endpoints and a real JSON object on POST endpoints - POST search routes still take pagination, sorting, date range, `view`, and `search_id` as query parameters; the JSON body is for `filter` and `filter_id` - `filter_id` is a 24-character transient context ID returned by the AI filter flow or prior searches - explicit `filter` overrides a stored `filter_id` context, and flat params may still be used in the same request - the same filter objects are reused by AI filter responses, exports, bulk search, and scanners - advanced filters use leaf rules with `field`, `operator`, and `value`, plus `and` / `or` groups for boolean logic - supported operators are `eq`, `neq`, `contains`, `starts_with`, `ends_with`, `wildcard`, `gt`, `gte`, `lt`, `lte`, `exists`, `in`, and `not_in` See the `StructuredFilterNode` schema and `/guides/structured-filters` for the full operator list and examples. ## Success Response Patterns Successful responses use three main patterns: - Envelope JSON: Common on search-session and OSINT endpoints, plus `v2/stealer/search`, `v2/breach/search`, `v2/victims/search`, `v2/stealer/subdomain`, and `v2/bulk-search` create. - Raw JSON: Common on `v2/breach/autocomplete*`, `v2/ai/filter*`, `v2/files/search`, `v2/victims/*/properties`, `v2/victims/*/summary`, `v2/file-search*`, `v2/exports*`, `v2/bulk-search` list and status, `v2/victims/{log_id}`, `v2/phonebook`, and most scanner endpoints. - File or text stream: Victim file downloads, victim archive downloads, export downloads, and bulk-search downloads. ## Error Handling API-generated errors generally return with `success: false` and include: - `message`: Human-readable error description - `errors`: Object with field-specific or general error details Common HTTP status codes: - `200`: Success - `202`: Async job accepted - `400`: Bad Request (invalid parameters) - `401`: Unauthorized (missing or invalid token) - `403`: Forbidden (Cloudflare block or quota exceeded) - `404`: Not Found - `409`: Conflict - `429`: Too Many Requests - `500`: Internal Server Error - `502`: Bad Gateway - `503`: Service Unavailable contact: name: OathNet Support url: https://oathnet.org/support license: name: Proprietary url: https://oathnet.org/terms servers: - url: https://oathnet.org/api description: Production API Server security: - ApiKeyAuth: [] tags: - name: Search Session description: Initialize and manage search sessions for grouped lookups - name: Breach Search description: Search across breach databases for leaked credentials and data - name: Stealer Search description: Original stealer search route for simple credential lookups - name: V2 Stealer description: Enhanced V2 stealer search with advanced filtering and pagination - name: V2 Investigation description: >- Multi-section investigation across credentials, victims, evidence, files, and related credentials - name: V2 Breach description: Current breach search, autocomplete, and filter workflows - name: V2 Victims description: Search and explore victim profiles and their associated files - name: V2 File Search description: Search within victim files using regex, literal, or wildcard patterns - name: V2 File Metadata description: Search victim file metadata without fetching file bytes - name: V2 Export description: Export search results to JSONL or CSV format - name: V2 Bulk Search description: Batch many terms into an asynchronous export-style search job - name: Scanners description: >- Automated monitoring and delivery management for stealer and breach scanners - name: OSINT Lookups description: Open Source Intelligence lookups for various platforms - name: Utility description: Utility endpoints for autocomplete and other helpers paths: /service/v2/victims/search: get: tags: - V2 Victims summary: Search Victim Profiles description: > Search victim summaries keyed by `log_id`. Successful responses use the standard search envelope. The same route also accepts POST when you want to send `filter` or `filter_id` in the JSON request body instead of the query string. Dashboard victim filters: - Identity and contact: `email`, `email_domain`, `username`, `discord_id`, `phone`, `steam_id`, `steam_name`. - Device and network: `ip`, `victim_ip`, `hwid`, `os`, `antivirus`, `infection_path`. - Geography and service: `country`, `city`, `domain`, `subdomain`, `service`, `identity_state`. - Volume and richness: `total_docs_min`, `total_docs_max`, `service_count_min`, `service_count_max`. - Metadata: `log_id`, date range via `from` / `to` and `date_field` (`pwned_at` or `indexed_at`). Structured filters can use the same bare victim field names above. When a filter is built from the full stealer investigation view, namespaced fields such as `victims.country`, `victims.service`, and `victims.total_docs` are projected to `country`, `service`, and `total_docs` for this direct victim search endpoint. operationId: searchVictimsV2 parameters: - name: q in: query schema: type: string - name: cursor in: query schema: type: string - name: page_size in: query schema: type: integer - name: sort in: query schema: type: string - name: from in: query schema: type: string format: date-time - name: to in: query schema: type: string format: date-time - name: date_field in: query schema: type: string enum: - indexed_at - pwned_at - name: wildcard in: query schema: type: boolean - name: log_id in: query schema: type: string - $ref: '#/components/parameters/StructuredFilterParam' - $ref: '#/components/parameters/FilterContextIdParam' - name: total_docs_min in: query schema: type: integer - name: total_docs_max in: query schema: type: integer - name: service_count_min in: query schema: type: integer - name: service_count_max in: query schema: type: integer - name: email[] in: query schema: type: array items: type: string style: form explode: true - name: email_domain[] in: query schema: type: array items: type: string style: form explode: true - name: ip[] in: query schema: type: array items: type: string style: form explode: true - name: hwid[] in: query schema: type: array items: type: string style: form explode: true - name: discord_id[] in: query schema: type: array items: type: string style: form explode: true - name: username[] in: query schema: type: array items: type: string style: form explode: true - name: country[] in: query schema: type: array items: type: string style: form explode: true - name: city[] in: query schema: type: array items: type: string style: form explode: true - name: os[] in: query schema: type: array items: type: string style: form explode: true - name: service[] in: query schema: type: array items: type: string style: form explode: true - name: steam_id[] in: query schema: type: array items: type: string style: form explode: true - name: steam_name[] in: query schema: type: array items: type: string style: form explode: true - name: phone[] in: query schema: type: array items: type: string style: form explode: true - name: domain[] in: query schema: type: array items: type: string style: form explode: true - name: subdomain[] in: query schema: type: array items: type: string style: form explode: true - name: identity_state[] in: query schema: type: array items: type: string style: form explode: true - name: victim_ip[] in: query schema: type: array items: type: string style: form explode: true - name: antivirus[] in: query schema: type: array items: type: string style: form explode: true - name: infection_path[] in: query schema: type: array items: type: string style: form explode: true - name: fields[] in: query schema: type: array items: type: string style: form explode: true - name: view in: query schema: type: string enum: - enriched - $ref: '#/components/parameters/SearchIdParam' responses: '200': description: Victim search response content: application/json: schema: $ref: '#/components/schemas/V2VictimsSearchResponse' components: parameters: StructuredFilterParam: name: filter in: query description: > JSON-encoded structured filter tree. Use leaf nodes with `field`, `operator`, and `value`, or compound nodes with `and` / `or`. If you would rather send the filter as a real JSON object, use POST on the same `/search` route. See `/guides/structured-filters` for the full grammar, operators, limits, and examples. schema: type: string example: >- {"and":[{"field":"country","operator":"eq","value":"us"},{"field":"email","operator":"ends_with","value":"@gmail.com"}]} FilterContextIdParam: name: filter_id in: query description: > 24-character transient filter context ID returned by `POST /service/v2/ai/filter` or a previous search response. schema: $ref: '#/components/schemas/FilterContextId' example: 0123456789abcdef01234567 SearchIdParam: name: search_id in: query description: Search session ID from `POST /service/search/init`. schema: type: string schemas: V2VictimsSearchResponse: type: object properties: success: type: boolean message: type: string data: $ref: '#/components/schemas/V2VictimsSearchData' FilterContextId: type: string description: 24-character transient filter context ID. pattern: ^[0-9a-fA-F]{24}$ example: 0123456789abcdef01234567 V2VictimsSearchData: type: object properties: items: type: array items: $ref: '#/components/schemas/V2VictimResult' meta: $ref: '#/components/schemas/V2SearchMetadata' next_cursor: type: string V2VictimResult: type: object properties: log_id: type: string device_users: type: array items: type: string hwids: type: array items: type: string device_ips: type: array items: type: string device_emails: type: array items: type: string discord_ids: type: array items: type: string total_docs: type: integer pwned_at: type: string format: date-time indexed_at: type: string format: date-time phone_numbers: type: array items: type: string steam_ids: type: array items: type: string steam_names: type: array items: type: string services: type: array items: type: string service_count: type: integer identity_state: type: string device_os: type: string device_country: type: string device_city: type: string infection_path: type: string antivirus: type: array items: type: string domains: type: array items: type: string subdomains: type: array items: type: string email_domains: type: array items: type: string victim_ip: type: string geo_country: type: string geo_city: type: string V2SearchMetadata: type: object properties: count: type: integer description: Results in this page total: type: integer description: Total matching results took_ms: type: integer description: Query time in milliseconds has_more: type: boolean total_pages: type: integer max_score: type: number filter_id: $ref: '#/components/schemas/FilterContextId' securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: API key for authentication (lowercase header name) ````