Feedback Records

Semantic search over feedback records

Embeds the search query and returns feedback record IDs with similarity scores (cosine, 0..1). Only available when embeddings are configured (EMBEDDING_PROVIDER and EMBEDDING_MODEL set). Supported providers: openai, google (Gemini Developer API / Google AI Studio), google-gemini (Gemini Enterprise Agent Platform API). When embeddings are disabled, this endpoint returns 503 Service Unavailable. Request body must include query and tenant_id (required for tenant isolation).

post/v1/feedback-records/search/semantic

Query parameters

limitinteger

Number of results to return (default 10, max 100). Consistent with list endpoints.

cursorstring

Example:eyJkIjowLjEsImkiOiIwMThlMTIzNC01Njc4LTlhYmMtZGVmMC0xMTExMTExMTExMTEifQ==

Omit for the first page. For the next page, use the exact value from the previous response's next_cursor. Opaque (base64-encoded); keyset pagination.

min_scorenumber float

Minimum similarity score (0..1); only results with score >= min_score are returned. Default 0.7 to reduce noise.

Request body

querystring required

Search query text (embedded and compared via cosine similarity)

tenant_idstring required

Tenant ID (required for isolation; must match feedback record tenant_id)

Example request

{
  "query": "What do users think about login speed?",
  "tenant_id": "org-123"
}

Response

limitinteger required

Limit used in query (echoed for consistency with list endpoints)

next_cursorstring

Opaque cursor for the next page (keyset paging). Present only when there may be more results (full page returned). Omit when no next page. Use this exact value as the cursor query param for the next page.

Example response

{
  "next_cursor": "eyJkIjowLjEsImkiOiIwMThlMTIzNC01Njc4LTlhYmMtZGVmMC0xMTExMTExMTExMTEifQ=="
}

Changes

Changed in 7 of the 35 revisions of this API.31024

Jun 26, 202617c77a1a30313See the full diff
- ●
  added the new content_too_large enum value to the code response property for the response status 400
  response-property-enum-value-added
- ●
  added the new content_too_large enum value to the code response property for the response status 503
  response-property-enum-value-added
- ●
  added the new content_too_large enum value to the code response property for the response status default
  response-property-enum-value-added
Jun 16, 2026d2fa5d9f2e983See the full diff
- ●
  added the new tenant_write_conflict enum value to the code response property for the response status 400
  response-property-enum-value-added
- ●
  added the new tenant_write_conflict enum value to the code response property for the response status 503
  response-property-enum-value-added
- ●
  added the new tenant_write_conflict enum value to the code response property for the response status default
  response-property-enum-value-added
Jun 3, 20266907a0a9de003318See the full diff
- ▲
  the instance response's property type/format changed from string/uri to string/ for status 400
  response-property-type-changed
- ▲
  the instance response's property type/format changed from string/uri to string/ for status 503
  response-property-type-changed
- ▲
  the instance response's property type/format changed from string/uri to string/ for status default
  response-property-type-changed
- ●
  removed the optional property errors from the response with the 400 status
  response-optional-property-removed
- ●
  removed the optional property errors from the response with the 503 status
  response-optional-property-removed
- ●
  removed the optional property errors from the response with the default status
  response-optional-property-removed
- ○
  added the optional property details to the response with the 400 status
  response-optional-property-added
- ○
  added the optional property details to the response with the 503 status
  response-optional-property-added
- ○
  added the optional property details to the response with the default status
  response-optional-property-added
- ○
  added the optional property invalid_params to the response with the 400 status
  response-optional-property-added
- ○
  added the optional property invalid_params to the response with the 503 status
  response-optional-property-added
- ○
  added the optional property invalid_params to the response with the default status
  response-optional-property-added
- ○
  the response property status became required for the status 400
  response-property-became-required
- ○
  the response property status became required for the status 503
  response-property-became-required
- ○
  the response property status became required for the status default
  response-property-became-required
- ○
  the response property title became required for the status 400
  response-property-became-required
- ○
  the response property title became required for the status 503
  response-property-became-required
- ○
  the response property title became required for the status default
  response-property-became-required
- ○
  added the required property code to the response with the 400 status
  response-required-property-added
- ○
  added the required property code to the response with the 503 status
  response-required-property-added
- ○
  added the required property code to the response with the default status
  response-required-property-added
- ○
  added the required property request_id to the response with the 400 status
  response-required-property-added
- ○
  added the required property request_id to the response with the 503 status
  response-required-property-added
- ○
  added the required property request_id to the response with the default status
  response-required-property-added
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Apr 30, 20262fe8dc460c4d3See the full diff
- ○
  the type response's property default value about:blank was removed for the status 400
  response-property-default-value-removed
- ○
  the type response's property default value about:blank was removed for the status 503
  response-property-default-value-removed
- ○
  the type response's property default value about:blank was removed for the status default
  response-property-default-value-removed
Mar 5, 20267af2577fe5922See the full diff
- ○
  the response property data/items/field_label became required for the status 200
  response-property-became-required
- ○
  the response property data/items/value_text became required for the status 200
  response-property-became-required
Mar 5, 2026a5a2961cda7b1See the full diff
- ●
  deleted the query request parameter offset
  request-parameter-removed
Mar 4, 2026b3611442ba191See the full diff
- ○
  endpoint added
  endpoint-added

Full history