Hi there,

I was under the impression, maybe falsely, that I could make a Twitter
Search request to api.twitter.com/1/search as well as
search.twitter.com, and I've been using the api.twitter.com for a
while now, mainly because I wanted to specify the version to prevent
version changes from breaking my code (which it has in the past).
However I'm now getting the different results from the two endpoints:

>From this endpoint:
https://api.twitter.com/1/search.json?q=superbikes

I get as a result:
{"statuses":
[40825857259,40827308851,40828019793,40830197255,40831193039,40832571529,40833377437,40833526201,40833626835,40834185577,40834533109,40835446369,40835933327,40836359953,40836960689,40837682441],"created_in":
0.008378}

Where as from:
https://search.twitter.com/search.json?q=superbikes

I get a correct response.

Which should I use? And how can I protect myself from major code
changes? Also, I can switch back to search.twitter.com, but I have an
App live in the App Store that was working great and now suddenly
isn't working because of this, and an update will be subject to a week
long delay by Apple. Please, please, please could you make
api.twitter.com/search match search.twitter.com at least for the next
week.

Many thanks,

Keith (@keefmoon)

Reply via email to