Steam Web API extremely slow.

[Lumiukko]

I am currently fooling around with the Steam Web API to retrieve some information for our small group. Basically who is playing with who (given their profiles are set to public).

The basic functionality is working fine, just the Steam Web API is extremely slow.
Often it is saying the service in at the moment unreachable.
If it is working, it sometimes takes up to 10 seconds to relieve the XML or JSON data.

I am using a normal HTTP request, e.g. to:
http://steamcommunity.com/profiles/<steamID>/?xml=1

Even with a normal web browser the retriaval takes ages...

Is it intented to be this unreliable, or is there a temporary problem?

[Lumiukko]

I need to bump this topic... maybe there are still people out there who also tried to use the API before and have an idea or something :)

[Jakk49 [lfgo.de]]

i use it too and i have the same problem, hope someone can help us :/
But i think this is normal..

[Waschbärpfötchen]

The Community Data is deprecated.
Instead use the Steam Web API.

[Lumiukko]

We discussed it also in another thread. The problem is, that the Steam Web API is not yet supporting all the access possibilities the old community data used to give us. But we are full of hope that this might change one glorious day :)

[Mr. Bubbles]

I recently created a steam id finder[www.vacbans.com] for looking up steam ID's, getting the age of private steam ID's and checking for VAC bans. It currently uses the XML version of the API because the JSON version lacks some of the info and is often slower. The download speed for the XML seems to match the download speed of a normal profile page. I think they have better servers than for the JSON web API.

[Khorne]

It's sad but one year late, the web API is still extremely slow. It can sometimes take up to 10 seconds (or more) to get an answer.

This is really not reliable.

[Ryvax]

yeah

[=)]

bump, the same

[デイヴィッド]

Here[www.firaja.cc] the solution guys

[Lumiukko]

Thanks for the article, I'm sure it will be helpful for most people arriving here :)

I can't speak for the current development, but at the time of the OP (more than 2 years ago), the API definitely was extremely slow. I myself was using curl since day 2 (or so) of my project, so that wasn't it. But it might have changed by now :)

[Khorne]

Originally posted by @firaja:

Here[www.firaja.cc] the solution guys :d2antimage:

Using curl is of course better than file_get_contents() but it doesn't change the fact that the Steam Web API is often very slow.

It takes usually around 0,2 / 0,3 seconds to get the answer from Steam Web API. And suddently around 9 seconds.

[q.q dodq1]

Yes

[Pwoire]

kaka-47