API problems - direct_messages

[bjhess]

Hi,

I'm not having any troubles with other API calls, but I'm getting a
500 when hitting direct messages:

https://user:pass...@twitter.com/direct_messages.xml

I've tried multiple users with no luck.

Any issues with the API right now?

Thanks!

~Barry

[bradley...@gmail.com]

I'm having the same issue, regardless of user. As with Barry,
everything else is working great.

On Mar 6, 1:34 pm, bjhess <bjh...@gmail.com> wrote:
> Hi,
>
> I'm not having any troubles with other API calls, but I'm getting a
> 500 when hitting direct messages:
>

> https://user:passw...@twitter.com/direct_messages.xml

[Cameron Kaiser]

> I'm not having any troubles with other API calls, but I'm getting a
> 500 when hitting direct messages:
>
> https://user:pass...@twitter.com/direct_messages.xml

It's affecting JSON also, and both http: and https:. I imagine the
Twitter guys are awere of it.

--
------------------------------------ personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * cka...@floodgap.com
-- Make welfare as hard to get as building permits. ---------------------------

[Alex Payne]

We're aware of it. One of our engineers made a change to the SQL
that's behind the direct messages request and it has issues in some
cases. We're working on a fix and it should be out real soon now. On
the upside, it should be faster once it works.

--
Alex Payne
http://twitter.com/al3x

[Fred Brunel]

Alex,

The API seems to work again but using the "since_id" parameter still
issue a 500 error.

[Alex Payne]

This should now be corrected as well, thanks for your report.

--
Alex Payne
http://twitter.com/al3x

[Fred Brunel]

It works. Thanks to the team.

[Barry Hess]

Yeah, thanks guys!