HTTP 500 Error usually means its a server error and its not your fault, however it may have something to do with your status post data. If you could, post the return headers and/or body. Also, it may have just been a simple problem with Twitter at the time. I just tested the API and it works fine for me: http://twitter.com/fastest963/status/1003271037 Maybe Alex or other devs can shed some light on something wrong with the Headers you sent.
- posting updates via js john
- Re: posting updates via js fastest963
- Re: posting updates via js John Greene
- Re: posting updates via js fastest963
