Skip to main content
Google’s search engine is built to surface the right information quickly, no matter how large your workspace has grown. Every document, record, tag, and annotation you store is indexed automatically, giving you full-text search across your entire dataset without any manual configuration. Whether you’re hunting for a report from six months ago, filtering by a specific data type, or building an automated pipeline that queries your workspace programmatically, this guide covers the tools and techniques you need to search with precision and confidence. The fastest way to search is directly from the search bar at the top of the dashboard. Type any keyword, phrase, or partial term and Google returns ranked results in real time as you type. Results include documents, records, notes, and any other data types your workspace contains. You can also perform a basic search through the REST API by sending a GET request to the /search endpoint:
Results are returned in descending order of relevance by default. Each result object includes the item’s id, title, type, score, and a short excerpt showing where the query term was matched.

Search Filters

Filters let you narrow results to a specific subset of your data. You can apply filters through the sidebar in the dashboard UI or by appending query parameters to API requests. Supported filter parameters: Combine multiple filters in a single request by chaining them with &:
You can stack multiple filter parameters in the same request. Google applies all filters with an implicit AND — results must satisfy every filter condition to appear in the response.

Advanced Query Syntax

For more precise control, Google supports a rich query syntax directly within the search term. You can use these operators in both the dashboard search bar and the q parameter of the API.

Sorting and Pagination

By default, results are sorted by relevance. You can change the sort order and control how many results are returned per page using the following parameters:
Sort and pagination parameters: Use page and limit together to page through large result sets. The response envelope includes a total field indicating the overall number of matching items, which you can use to calculate the number of available pages.

Search via API

For full programmatic access, use the search endpoint with your API key and optional request body filters. The example below performs a filtered, paginated search and shows the expected response shape:
Example JSON response:
Newly created or updated items may take a few seconds to appear in search results due to indexing latency. If you’ve just added data and don’t see it yet, wait 5–10 seconds and try your query again. For near-real-time use cases, use the direct item retrieval endpoint (GET /v1/items/:id) rather than search.