The answers parameter was recently added to most of the requests that return a list of questions. See: Don’t include answers in question lists by default
It looks like the /search request got left out. It appears to never return answers.
Add a comment
|
2 Answers
This is [by-design].
/search is already pretty resource intensive, and not returning answers is a conscious effort to reduce its runtime.
The answers parameter does not appear in the documentation for /search accordingly.
The /search/excerpts route looks to be about as good as /search and it does return both questions and answers, and it does have an answers parameter.
This route is "★ All new! For version 2.2! ★"
