StarCraft2: US and KR profile API endpoints return 503

API Bug Report
1

The US region broke down on 2024-11-02, about 07:00:00 UTC
The KR region broke down on 2024-11-03, also around 07:00:00 UTC

Endpoints. I assume other profile endpoints are broken too.

/sc2/profile/:regionId/:realmId/:profileId/ladder/:ladderId 
/sc2/profile/:regionId/:realmId/:profileId/ladder/summary
/sc2/legacy/profile/:regionId/:realmId/:profileId/matches

Examples

https://eu.api.blizzard.com/sc2/profile/1/1/5058074/ladder/summary
https://us.api.blizzard.com/sc2/profile/1/1/5058074/ladder/325813
6 Likes
2

Can confirm. Not working here either.

2 Likes
3

I can also confirm the issue.

2 Likes
4

The EU region API doesn’t work now either. Same as in US and KR regions, profile endpoints return 503 error.

1 Like
5

I was about to write the same just now. Good that you reported it but we both know how will that going to end :).

2 Likes
6

This has been passed along to be investigated. Thanks for the reports :wave:

9 Likes
7

I think there is a problem with the Account API as well:

https://eu.api.blizzard.com/sc2/player/:accountId

Returns 404 for all queries.

2 Likes
8

Sorry there haven’t been any updates yet. It’s still on the radar though!

4 Likes
9

I’ve received a report back that these should be returning results again. Please try / check.

4 Likes
10

Yes it worked for about 4 hours, but now it’s dead again unfortunately. Thanks for the feedback though! Is it possible to fix it again for a longer time?

1 Like
11

Passed along the new report, thanks for trying it.

4 Likes
12

API endpoints seem to work atm. I hope those are stable now.
I must say I’m pleasantly surprised that the issue was addressed and fixed! Thank you Kalviery for passing it along and thanks to dev team for the fix.

3 Likes
13

It did hold longer this time, but it’s kind of dead again, with the exception of US, that still works at the time of writing this message.

Last successful reply:

  • KR at 2024-11-13 07:50:32 (see https://i.imgur.com/biiiBPS.png)
  • EU at 2024-11-13 17:43:12 (see https://i.imgur.com/jZW4NNB.png)

In both cases the ratio of 200 had decreased in favour of 503 few hours before these died.

Some charts showing 503 on the timeline, if they’re any helpful:

  • US - https://i.imgur.com/zAsmSqo.png - (still works)
  • EU - https://i.imgur.com/1ixZxFb.png
  • KR - https://i.imgur.com/FSTaS8m.png

All timestamps are in UTC.

2 Likes
14

This is a follow up of a recent SC2 BNet api bug report (which I cannot link here) that was fixed. Unfortunatelly we are back to square one :frowning: .Endpoints that don’t work for EU and KR regions:
/sc2/legacy/profile/:regionId/:realmId/:profileId/matches
/sc2/profile/:regionId/:realmId/:profileId/ladder/summary
/sc2/metadata/profile/:regionId/:realmId/:profileId

Response error code: 503

2 Likes
15

Thanks for the continued reports. The root cause is still being investigated, so we may still see some instability with these services until that can be resolved.

4 Likes
16

The API has been stable for the past few days in my case, but the US gateway(us.api.blizzard.com) returns 504 error. If I change the gateway to EU or KR and make the same API calls for US profiles, then everything works. Some endpoints return 504 in all gateways(regions), for example the account endpoint /sc2/player/:accountId. There may be more, be that’s what we have verified atm.

I hope this info will be useful. Thanks for your continued efforts to fix it, we all really appreciate it!

1 Like
17

IMHO, this implies it hasn’t been stable. But well - yes relatively more stable and predictable, if we were to compare it with the initial situation, where almost nothing was working.

Yeah. However, this doesn’t affect all accounts, for instance player/1 works reliably. But something that doesn’t work (504), will continue not working no matter how many times you gonna try (okay, fine - I didn’t do more than 10-20 attempts spread across hours/days - calling for the same profileid).

http -p=b https://eu.api.blizzard.com/sc2/player/1 "Authorization:Bearer $BATTLE_TOKEN"
[
    {
        "avatarUrl": "https://static.starcraft2.com/starport/bda9a860-ca36-11ec-b5ea-4bed4e205979/portraits/1-32.jpg",
        "name": "avblue",
        "profileId": "267409",
        "profileUrl": "https://starcraft2.blizzard.com/profile/1/1/267409",
        "realmId": 1,
        "regionId": 1
    }
]

(However, if I were to change eu.api to us.api it’d return 504, like it does for everything else I’ve tested thus far on this gateway).

My best guess is it’s because this account is inactive. So in all practical uses of this this endpoint it’ll likely return error, or at least that’s what it was doing for my account, and some others who attempted to verify via website.

2 Likes
18

Further testing does seem to confirm that theory.
My old account (125390537) that I didn’t login into for years:

$ http -p=b https://eu.api.blizzard.com/sc2/player/125390537 "Authorization:Bearer $BATTLE_TOKEN"
[
    {
        "avatarUrl": "https://static.starcraft2.com/starport/bda9a860-ca36-11ec-b5ea-4bed4e205979/portraits/0-0.jpg",
        "name": "josgon",
        "profileId": "2273574",
        "profileUrl": "https://starcraft2.blizzard.com/profile/2/1/2273574",
        "realmId": 1,
        "regionId": 2
    }
]

My current account (128747765) that I use actively in SC2 (Talv#2620):

$ http https://eu.api.blizzard.com/sc2/player/128747765 "Authorization:Bearer $BATTLE_TOKEN"
HTTP/1.1 504 Gateway Timeout
Connection: keep-alive
Content-Length: 0
Content-Type: text/plain;charset=utf-8
Date: Mon, 18 Nov 2024 20:59:08 GMT
X-Content-Type-Options: nosniff
blizzard-token-expires: 2024-11-19T20:36:51.146Z
server: blizzard
x-frame-options: SAMEORIGIN
x-trace-parentspanid: 180575ac-e971-0e50-e2a6-fa165bc8e78b
x-trace-spanid: 180575ac-e97d-1a50-e2a6-fa165bc8e78b
x-trace-traceid: 772b69ca-480d-34ef-b240-8de54a592b09

EDIT 1

Actually, scratch that. I don’t really see the pattern here, tried some other accoutns such as 466518383 , which is currently online (seen acctivity less than 1h ago). And it replies fine:

❯ http https://eu.api.blizzard.com/sc2/player/466518383 "Authorization:Bearer $BATTLE_TOKEN"

HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Cache-Control: no-cache
Connection: keep-alive
Content-Length: 486
Content-Type: application/json; charset=utf-8
Date: Mon, 18 Nov 2024 21:13:14 GMT
ETag: W/"1e6-e3smD28oDOmnqwBOnshXZ+u7fIM"
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
X-Powered-By: Express
blizzard-token-expires: 2024-11-19T20:36:51.146Z
server: blizzard
x-frame-options: SAMEORIGIN
x-trace-parentspanid: 18057672-adfa-3590-227c-fa165bb18be7
x-trace-spanid: 18057672-adfa-35c0-227c-fa165bb18be7
x-trace-traceid: 3d67e26a-64c5-34dd-b623-8adc4722b914

[
    {
        "avatarUrl": "https://static.starcraft2.com/starport/bda9a860-ca36-11ec-b5ea-4bed4e205979/portraits/15-14.jpg",
        "name": "Pixie",
        "profileId": "10277433",
        "profileUrl": "https://starcraft2.blizzard.com/profile/1/1/10277433",
        "realmId": 1,
        "regionId": 1
    },
    {
        "avatarUrl": "https://static.starcraft2.com/starport/bda9a860-ca36-11ec-b5ea-4bed4e205979/portraits/1-32.jpg",
        "name": "Pudding",
        "profileId": "8246237",
        "profileUrl": "https://starcraft2.blizzard.com/profile/2/1/8246237",
        "realmId": 1,
        "regionId": 2
    }
]

Still, majority of the calls is not working (504).

2 Likes
19

Is the API working again or no?

I’m trying to test the /sc2/profile/:regionID/:realmID/:profileId endpoint from Blizzard Battle.net Developer Portal and it keeps giving me “The following required parameters were missing or invalid: regionId” even though I am passing in a region ID.

20

Personally I’m not seeing any issues for at least a week. These endpoints are stable for me, on all regions:

  • /sc2/legacy/profile/:regionId/:realmId/:profileId/matches
  • /sc2/metadata/profile/:regionId/:realmId/:profileId
  • /sc2/player/:accountId

The issue reported originally appears to be resolved at the time of writing this message.