Timeline for Would it be possible (in a future API release) to combine queries?
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 13, 2017 at 12:25 | history | edited | CommunityBot |
replaced http://stackapps.com/ with https://stackapps.com/
|
|
S Dec 24, 2013 at 4:12 | history | suggested | michaelb958--GoFundMonica | CC BY-SA 3.0 |
[request] is a Thoroughly Useless Tag™; updated request to reflect state of 2.x API
|
Dec 24, 2013 at 1:16 | review | Suggested edits | |||
S Dec 24, 2013 at 4:12 | |||||
Jul 2, 2011 at 19:35 | comment | added | Jonathan. | Thanks nice to know it's in the [rather long] pipeline :) | |
Jul 2, 2011 at 19:16 | comment | added | Nathan Osman | @Jonathan: I found this quote here: "...and for the ability to request only a subset of the fields on an object..." | |
Jun 30, 2011 at 12:57 | comment | added | Jonathan. | yes I know :) thats why I commented :). But it would solve your problem, use less bandwidth, and be more efficient, in one swoop. | |
Jun 30, 2011 at 1:19 | comment | added | Nathan Osman | @Jonathan: That would be nice too but one thing at a time :) | |
Jun 29, 2011 at 16:27 | comment | added | Jonathan. |
I don't if it would be possible, but I'd like to be able to choose what is returned, so if you call http://api. {SITE} .com/1.1/users/ {ID} you can set either through HTTP header fields or URL parameters or POSTing some JSON, what fields you want to be returned, eg you might only want the user's display name, and nothing else, but you might what their favourite questions, tags, etc all in one.
|
|
Jun 29, 2011 at 0:29 | history | asked | Nathan Osman | CC BY-SA 3.0 |