Skip to main content
This endpoint lets you search for relevant passages of up to 100 PDF documents by using advanced filters and semantic search queries. Where documents search results in a list of relevant documents, this endpoint gives you a result of the most relevant parts of a set of documents. For each query you have to specify a list of document ids using the in filter (see example). Semantic search works by comparing the semantic meaning of the search query to the semantic meaning of the document passages. The document passages are automatically derived and indexed upon file uploads (PDF only). A natural flow would be:
  1. Upload a document
  2. Query /documents/status to check if the document is ready (see beta documentation)
  3. Query /documents/passages/search to find relevant passages in the document(s)

​
Passages search offers semantic search filters

This endpoint requires a list of document ids that you want to do semantic search on. You can not currently search through all passages for the entire project in a single query.

​
Ordering

Search results are ranked by relevance, with the most relevant appearing first. How relevance is determined depends on the filter you choose:
  • Lexical Search Filter: This filter looks for exact word matches, making it ideal for finding specific dates, names, or keywords. Use this when you know exactly what you’re looking for. This is the default search behavior for the Documents API.
  • Semantic Search Filter: This filter understands the meaning behind words and phrases, even if they don’t match exactly. It’s useful for broader searches or when you’re looking for related ideas or concepts.
Choose the filter based on your needs: use Lexical for precise results and Semantic for more general, context-based searches. When both filters are used together, the results are combined to give you a balanced, relevant list. For best results, we recommend starting with both filters active.

​
Examples

The following request will return document passages matching the specified search query for the document ids 1, 2, and 3. 
{
    "filter": {
        "and": [
            {
                "semanticSearch": {
                    "property": ["content"],
                    "value": "I have an overheating pump that is 85 degrees celsius, what dangers are there with higher temperatures"
                }
            },
            {
                "in": {
                    "property": ["document", "id"],
                    "values": [1, 2, 3]
                }
            }
        ]
    }
}
If you need keyword matching you can specify a lexicalSearch filter. This helps with edge cases where it’s hard to extract meaning such as numbers (eg. dates), names, etc. 
{
    "filter": {
        "and": [
            {
                "semanticSearch": {
                    "property": ["content"],
                    "value": "I have an overheating pump that is 85 degrees celsius, what dangers are there with higher temperatures"
                }
            },
            {
                "lexicalSearch": {
                    "property": ["content"],
                    "value": "pump AJ523-253-133"
                }
            },
            {
                "in": {
                    "property": ["document", "id"],
                    "values": [1, 2, 3]
                }
            }
        ]
    }
}
Doing just lexical search is also possible: 
{
    "filter": {
        "and": [
            {
                "lexicalSearch": {
                    "property": ["content"],
                    "value": "pump AJ523-253-133"
                }
            },
            {
                "in": {
                    "property": ["document", "id"],
                    "values": [1, 2, 3]
                }
            }
        ]
    }
}

​
Filtering

Filtering uses a special JSON filtering language. It’s flexible and consists of a number of different “leaf” filters, which can be combined arbitrarily using the boolean clauses and. This is the same filters used in the search, list and aggregate endpoints, with some restrictions and the addition of “semanticSearch” filter.

​
Supported leaf filters

Only includes results that are equal to the specified value. Supported fields: Non-array type fields.
{
    "equals": {
        "property": ["property"],
        "value": "example"
    }
}
Only includes results that are equal to one of the specified values. Supported fields: Non-array type fields.
{
    "in": {
        "property": ["property"],
        "values": [1, 2, 3]
    }
}
Supported fields: content.
{
    "semanticSearch": {
        "property": ["property"],
        "value": "example"
    }
}
Supported fields: content.
{
    "lexicalSearch": {
        "property": ["property"],
        "value": "example"
    }
}

​
Properties

The following overview shows the properties you can filter on and which filter applies to which property.
PropertyTypeApplicable filters
["document", "id"]integerequals, in
["document", "externalId"]stringequals, in
["document", "instanceId"]objectequals, in
["type"]stringequals
["content"]stringsemanticSearch, lexicalSearch

​
Full example

{
    "filter": {
        "and": [
            {
                "in": {
                    "property": ["document", "instanceId"],
                    "values": [
                        {"space": "space1", "externalId": "my-ext-id-1"},
                        {"space": "space1", "externalId": "my-ext-id-45"},
                        {"space": "space1", "externalId": "some-other-ext-id"}
                    ]
                }
            },
            {
                "semanticSearch": {
                    "property": ["content"],
                    "value": "A person walking a dog at night time"
                }
            },
            {
                "lexicalSearch": {
                    "property": ["content"],
                    "value": "11:23pm"
                }
            }
        ]
    }
}
Last modified on April 23, 2026