Skip to main content
The Quick Search endpoint runs a search synchronously and returns results directly in the response. A Search object is still created and counts toward your quota, but unlike Advanced Search you don’t need to poll for results — they’re returned immediately.

Request body

array
required
Array of category IDs to include in the search results.
string
Additional context for the AI to tailor the search and reporting (for example, your organization or focus area). Maximum 1000 characters.
string
required
A list of policy topics to search for, one per line. Longer, descriptive phrases work best. Maximum 5000 characters.
object
A dictionary of string key-value pairs for your own record keeping. Use this to attach metadata to the search, such as the project or team it belongs to (for example, {"project": "tax-reform", "team": "policy"}).
boolean
Set to true to validate the request and return example data without running a source search. Required fields such as categories, filter_prompt, and date_range are still validated normally.
object
Custom dummy data to return when is_test is true. Quick Search only supports custom search_results; it does not support custom edited outputs.
object
required
Time period to search within. Must cover no more than 72 hours (3 days) — use either start_date/end_date or duration_seconds ≤ 259200.

Response

array
Array of search result objects.
string | null
Error message if an error occurred; otherwise null.
boolean
Whether the Search was created in test mode.

Test mode

Use is_test: true to test your integration without running a source search. The endpoint still validates the request body the same way it does for a normal Quick Search request.
Example test request body