Skip to content

Add group search and autocomplete API endpoints#4043

Closed
mintlify[bot] wants to merge 1 commit intomainfrom
add-group-search-api-1772761110
Closed

Add group search and autocomplete API endpoints#4043
mintlify[bot] wants to merge 1 commit intomainfrom
add-group-search-api-1772761110

Conversation

@mintlify
Copy link
Contributor

@mintlify mintlify bot commented Mar 6, 2026

Summary

  • Added two new Assistant API endpoints for group-based search
  • Search over groups: Search documentation chunks grouped by page
  • Autocomplete over groups: Real-time autocomplete with results grouped by page

Both endpoints support filtering by version, language, and other criteria, with configurable highlight options and pagination.


Note

Low Risk
Documentation-only update that expands the published Assistant API surface (new endpoints/schemas) but does not change runtime behavior; main risk is spec/contract mismatches if the backend doesn’t match the new definitions.

Overview
Adds two new Assistant search endpoints documented as group/page-based results: POST /v1/search/{domain}/groups and POST /v1/search/{domain}/groups/autocomplete (plus new MDX reference pages).

Updates the OpenAPI specs (discovery-openapi.json and localized variants) with new request/response schemas (GroupSearchBody, GroupAutocompleteBody, GroupSearchResponse, filters, highlight options, and error shape), and wires the new pages into docs.json navigation for EN/FR/ES/ZH (with minor FR text punctuation fixes).

Written by Cursor Bugbot for commit 7337f80. This will update automatically on new commits. Configure here.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

},
"max_length": {
"type": "integer",
"exclusiveMinimum": 0,
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Numeric exclusiveMinimum invalid in OpenAPI 3.0.1 spec

Medium Severity

The spec declares "openapi": "3.0.1" but uses "exclusiveMinimum": 0 as a numeric value, which is only valid in OpenAPI 3.1+. In OpenAPI 3.0.x, exclusiveMinimum is a boolean modifier for minimum, not a standalone numeric constraint. This means parsers and validation tools following the 3.0.x spec will either reject the schema or misinterpret the constraint — potentially allowing 0 for fields like page_size, group_size, max_length, max_num, and window where the intent is to require values greater than zero. The correct 3.0.1 form is "minimum": 1 for integers, or "minimum": 0, "exclusiveMinimum": true. This same issue exists in all four locale files.

Additional Locations (2)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant