Skip to main content
Well-constructed queries determine the quality of your CatchAll results. This guide shows you how to write queries that return focused, relevant events.

​
Quick checklist

Before submitting a query, review these recommendations:
Testing queries: For quick testing, submit a job with the limit parameter to process fewer records (e.g., limit: 10). Once satisfied with the results, continue the job or adjust the query and create a new job.

​
What CatchAll finds

CatchAll, by design, focuses on identifying and extracting real-world events — things that actually happen and get reported. The system queries a continuously updated index of 2+ billion web pages, featuring time-sensitive, event-driven content. CatchAll is for finding events:
  • Acquisitions, funding rounds, product launches
  • Regulatory approvals, recalls, legal rulings
  • Executive changes, layoffs, facility openings
CatchAll is not for static content:
  • Product specifications or historical data tables
  • Educational content, how-to guides, or reference material
  • Evergreen articles or encyclopedic content
CatchAll vs traditional web search:
  • Traditional web search: “Information about clinical trials” → Articles explaining what clinical trials are
  • CatchAll: “Phase 3 clinical trial results for oncology drugs” → Every specific trial result with efficacy data, statistical significance, and trial identifiers

​
Specify event type

An event is something that happens and gets reported. CatchAll can only find events that appear in published content—if something happens but isn’t reported anywhere, it’s not observable to the system. Target recognizable event types that get consistently reported:
This list is not exhaustive. CatchAll can find any event type that gets reported across authoritative web sources. If you can describe “what happened,” CatchAll can find it.

​
Add 2-4 details

Balance breadth and focus. Too few details returns everything; too many details returns nothing. Add 2-4 details like industry, threshold, or geography.
Use the context parameter for extraction preferences. Keep your query focused on the core event.

​
Specify timeframe in your query

To scope your results to a specific period, include a timeframe in your query. If you don’t, the system uses a 5-day default. Your plan determines the maximum search depth available to you. You can also set the timeframe directly using start_date and end_date in the request.
To learn how search depth and date ranges work, see Index and search depth.
For monitors, the system automatically adapts time-based filters for recurring execution. See Configure monitors for monitor-specific guidance.

​
Keep queries focused

Focused queries produce cleaner, more useful results. If your query combines multiple entities or event types, consider splitting it into separate queries.

​
See also