Search inside a single knowledge table
Semantic search with relevance reranking limited to one knowledge table, identified by its uuid (the Knowledge Id shown on the table page). The table must be indexed for search (synced, or added to general search).
Authorizations
Use a Bearer token to access these API endpoints. Example: "Bearer {your-token}"
Path Parameters
Body
"What is the price of the Peugeot 3008?"
1 <= x <= 205
0 <= x <= 10.35
Page of the matched rows
x >= 11
Matched rows per page
1 <= x <= 10015
Response
Search results
true
"Search completed"
The excerpt view: the text chunks that matched.
The table's columns in schema order — same shape as the records listing, so matches can be rendered in the same grid.
The matched records as table rows, best match first, keyed by column name. A record that produced several matching chunks appears once, scored by its best chunk. Records deleted since the last index are omitted.
Page state over the matched rows. Search returns a ranked top-N (see limit), so this pages that result set rather than the whole table. next_page_url points at this same POST endpoint — resend the body with it.