[twitter-dev] Re: 401 error from CRON job

[e.p.c.]

On Jun 8, 12:35 pm, tomofo ross.mckeg...@gmail.com wrote:
 Throws the error:
 GEThttp://twitter-api-app11.apigee.com/1/account/verify_credentials
 401: Could not authenticate with OAuth.

Maybe I'm missing something, but 1) I didn't think twitter uses apigee
and 2) when fetch that URL I get Requested Domain twitter-api-
app11.apigee.com not registered and a 404 HTTP status. Why are
you going against apigee.com for the twitter API?
--
-ed costello

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: 401 error from CRON job

[tomofo]

Apigee is a proxy to Twitter; gives you significantly higher usage caps. 

I replaced my Apigee Id with 111.

The real question is: has anyone used Apigee and Twitter for protected 
functions like status updates or (as I'm trying to do) add users to a list.


-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk