Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with parameters
Search options questions only
not deleted
user 14
for question about the use of parameters when calling the Stack Exchange API
0
votes
1
answer
151
views
min/max parameters are incorrectly documented as date - confusion and crippled libraries ensue
I have noticed this on all sorted routes.
The min/max say that they are context sensitive to the sort type yet are documented as date.
How is a date min/max valid when sorting by, for instance votes …
- 12.1k
2
votes
1
answer
52
views
Why does /users/{id}/answers, which returns an array of answers, have an optional 'answers' ...
I would assume that if you are requesting the route '/users/{id}/answers' that you wish to receive some answers.
- 12.1k
7
votes
0
answers
119
views
API Parameters: Consolidated Observations
A consolidate view of the API parameters can be seen using param-exam.
order parameter description is inconsistent.
They could be replaced with How the current sort should be ordered. … /search
/users
/users/{id}
min and max parameters are incorrectly typed as date.
They could be better typed as string. …
0
votes
1
answer
98
views
/questions/tagged/{tags} - tags param clarification
This API method has been removed as of Jul 16 '10. The original question is preserved below for posterity.
It is not clear what a "list" of {tags} looks like.
Does this parameter follow the s …
- 12.1k