Fix /search curl example: wrap text in contents object #3
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.
Summary
Fixes the "Simple search and contents" curl example for the
/searchendpoint. The example was using"text": trueat the top level, which is silently ignored by the API. Thetextparameter must be wrapped in acontentsobject.Before (broken):
{"query": "...", "text": true}After (working):
{"query": "...", "contents": {"text": true}}The Python and JavaScript SDK examples work correctly because the SDKs handle this transformation internally.
Review & Testing Checklist for Human
contentswrapper is the correct structure per API implementationNotes
Part of a docs audit finding behavior mismatches between documentation and actual API behavior. Other issues being addressed in separate PRs.
Link to Devin run: https://app.devin.ai/sessions/616457e78aea475481e0607e4f176b40
Requested by: Michael Fine (@mfine15), PRs requested by Ishan Goswami