3
The API currently does not support this, but then neither does the website itself.
The "How do I search?" help page says:
OR operator
To combine results from multiple tags, separate the tag names (enclosed in square brackets) with the word "or": [widgets] or [geegaws] returns questions tagged with either tag.
(Emphasis added)
Note that it only ...
3
Although it doesn't appear to say so in the doc page, intitle expects an exact phrase, not a list of words.
You can currently see this by:
/2.2/search?intitle=get column array&site=stackoverflow
which currently returns one result with that exact phrase in the title, but doesn't return the many questions that have those 3 words in other arrangements.
...
2
The /search path and the /search/advanced path return only questions, not answers, and by design. It says so right in the doc pages:
Searches a site for any questions which fit the given criteria.
and
This method returns a list of questions.
Your example Stack Overflow search returned answers as well.
The correct equivalent search is:
...
2
This was a search issue in elastic (max_result_window) that has now been tuned across the network.
See, also, this related Q&A on Meta SE.
2
In order to get the total, you need to use a filter that includes it.
If you just want the total, as your sample code implies, then use the built-in total filter. For example:
/2.2/search?intitle=X&site=stackoverflow&filter=total
If you want the total AND the results, then you must use a custom filter with the ...
2
Date parameters are in unix epoch time and 1447113600 is 2015-11-10, 00:00:00.
So any questions posted on Nov 10th actually happened after that.
When searching for date ranges, you usually want to increment the end-date (max in this case) by one full day.
For example, if you want items from 12-12-2012 to 12-13-2012, you would use max=1355443200 (The ...
1
The /search/excerpts method supports searching by tag and returns the excerpts you're looking for:
1
No, there is no easy way to do this via the API.
Related feature requests:
Provide a method to search for sites winch merely wanted a search for site name/description. It was declined.
Search across Stack Exchange sites in Android app. To implement this usually would mean that a supporting method would be added to the API. This feature-request has been ...
1
No there is no "Query API", especially not for SQL-like syntax.
It sure would be sweet to have an always current version of SEDE† (even if limited to, say, a hundred rows), but this is very unlikely to ever be provided.
Your options are:
Oftentimes the q parameter of the /search/advanced route is pretty powerful and will get you close to what you ...
1
Is there any valid way to get the information from stackoverflow.com/search?q=?
Use the /search/advanced route of the API; that's what it's there for.
For example:
/2.2/search/advanced?q=foo&tagged=python&site=stackoverflow
(Doc page equivalent)
1
I forget when, but sometime in the last couple of years, the /search/excerpts route started allowing is:answer in the q parameter.
For example:
/2.2/search/excerpts?&q=Hear! is:answer&site=stackapps
-- which returns Stack Apps answers with the text "Hear!" in the body.
(Pretty sure I tested this in early 2014, ...
1
Looks like no data from May 2013 onwards:
http://data.stackexchange.com/stackoverflow/query/154032/phonegap-posts-by-month
When I search for the phonegap tag on SO:
...and click the button I get taken to questions tagged cordova:
I suspect the tags have been merged?
1
The search path already allows more than 5 tags, and it uses OR logic. From the docs:
tagged and nottagged are semi-colon delimited list of tags. At least 1 tag in tagged will be on each returned question if it is passed, making it the OR equivalent of the AND version of tagged on /questions.
(bold added)
Note that tags are separated with a semicolon, ...
1
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! ★"
Only top voted, non community-wiki answers of a minimum length are eligible
