Keyword Search

Performs keyword search across multiple documents and returns matches without positional information for faster response times.

Key Features:

  • Faster than batch search (no positional data retrieval)
  • Each match includes a unique match_id
  • Use match_id with the positional-info endpoint to get positions on demand
  • Supports same filtering and search options as batch search

Use Cases:

  • Initial search to find relevant documents quickly
  • When positional information is not immediately needed
  • Two-step workflow: search first, then get positions for specific matches

Workflow:

  1. Use this endpoint to quickly find matching documents
  2. Review results and identify matches of interest
  3. Call the positional-info endpoint with match_id for precise locations
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

V3 batch-search request.

Same shape as :class:BatchSearchRequestSerializer but nests the v3 filters
serializer, which drops the deprecated periods field.

keywords
array of strings
required
length between 1 and 10

List of keywords to search for (1-10 keywords)

keywords*
filters
object

V3 batch-search filters.

Same shape as :class:BatchSearchFiltersSerializer but without the deprecated
periods field (and thus no LegacyFieldAliasMixin). Kept as a standalone
class so it is trivial to delete once v2 is sunset.

options
object

Serializer for batch search options.

Headers
string
enum
Defaults to application/json

Generated from available request content types

Allowed:
Responses

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json