Get short, timely messages from Twitter API.

Twitter is a rich source of instantly updated information. It's easy to stay updated on an incredibly wide variety of topics. Join today and follow @twitterapi.

Get updates via SMS by texting follow twitterapi to your local code.
Codes for other countries

Two-way (sending and receiving) short codes:
Country Code For customers of
Australia
  • 0198089488 Telstra
Canada
  • 21212 (any)
United Kingdom
  • 86444 Vodafone, Orange, 3, O2
Indonesia
  • 89887 AXIS, 3, Telkomsel
Ireland
  • 51210 O2
India
  • 53000 Bharti Airtel, Videocon
Jordan
  • 90903 Zain
New Zealand
  • 8987 Vodafone, Telecom NZ
United States
  • 40404 (any)

twitterapi

  1. Some users are experiencing issues with the CAPTCHA on app registration; we're working to resolve the problem. Thanks for the notes! ^TS
  2. @JasonStoltz @unsay @maxdovey Thanks for the pointer! We'll look into this right away. ^TS
  3. @maxdovey no, why would we do that? It appears to be a temporary issue with REcaptcha; will continue investigating. ^TS
  4. @maxdovey looks like reCAPTCHA had a service interruption of some kind; looks to be resolved. ^TS
  5. @geekettebits No timetable unfortunately. ^TS
  6. @jasperdevalk increased rate limits are no longer offered; for NodeXL projects you'll just have to spend a bit more time. ^TS
  7. @alexmarkley Auto link shortening is not yet supported widely on the platform but will be automatic someday. ^TS
  8. @jelder No support in the API for these features yet. Tweet read status is often at conceptual odds with how tweets are consumed. ^TS
  9. @JDNebusiness this is a bug we're looking into. thanks. ^TS
  10. @dannydearlove this is a bug we're looking into. thanks. ^TS
  11. @gussyboy81 @support It doesn't look like you're including platform.twitter.com/widgets.js on the page ^TS
  12. @sferik There are few times where a remote app would show the developer TOS to a Twitter end-user, the site-wide TOS is another story. ^TS
  13. @yoshi32 not sure I understand your question, try asking on our mailing list? ^TS
  14. @emrahgunduz a REST principle is that write actions should never be executed via a GET. ^TS
  15. @jelder it's not likely, but I wouldn't rule it out either. ^TS
  16. @Oprius It doesn't need to say "What's happening?" it also shouldn't say anything misleading - it should be clear what's going to happen ^TS
  17. @sferik Interesting idea, maybe someday. ^TS
  18. @sferik I'm not sure I understand the question; you want an API to GET the dev TOS? HTTP GET http://t.co/H4gOHLJ ;) ^TS
  19. @daremon we're looking into it; thanks for reporting! ^TS