Restore /content/search schemas to Preview spec#546
Merged
Conversation
Re-adds the GET /content/search path and the five content_search_* component schemas that were silently removed by sync PR #518. Matches runtime behavior of Api::V3::Content::SearchController: - query is optional (returns most recent when omitted), maxLength 500 - per_page defaults 10, max 50 - page defaults 1, minimum 1 Supersedes the inlined-schema design of developer-docs PR #942 with the named-schema design from OpenAPI PR #513, so the path block can be cleanly extended by the planned Tier-1 filter wave.
bhavishnadar
approved these changes
Jun 9, 2026
bhavishnadar
left a comment
bhavishnadar
left a comment
Contributor
There was a problem hiding this comment.
Thanks a mil @kilian-tennyson
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why?
The
GET /content/searchendpoint is live in production but missing from the Preview spec. It was originally documented in #513 (merged 2026-05-22), then silently removed four days later by sync #518 — a 2,097-line docs sync that dropped schemas not yet present in the source repo's main branch. The endpoint is invisible to SDK generation as a result.How?
Re-adds the path block and five
content_search_*component schemas (withoneOf+typediscriminator), plus a newContenttag betweenContactsandContent Snippets. Schema matches the runtime contract:queryis optional (returns most recent when omitted), maxLength 500per_pagedefaults 10, max 50pagedefaults 1, minimum 1Validated locally — YAML parses cleanly,
npx fern-api checkpasses, diff is purely additive (1 file changed, 246 insertions, 0 deletions). Unblocks planned filter-parameter extensions to/content/search.Coordination
A competing inlined-schema approach exists in the docs source repo. This PR supersedes that approach with the named-schema design from #513 (plus a `query: required: false` correction matching runtime). A sibling docs-side PR mirroring this shape will follow.
Generated with Claude Code