Hi everyone,
currently the D3 item api seems to be very unstable. What was just “alive” is “dead” in the other second and vice versa.
My request looks like this:
Region: EU
Path: /d3/data/item/blackhand-key-Unique_Wand_006_x1
Locale: en_US
https://eu.api.blizzard.com/d3/data/item/blackhand-key-Unique_Wand_006_x1?access_token=token&locale=en_US
Sometimes the request returns this 404 response:
404 response
HTTP/1.1 404 Not Found
Date: Tue, 19 Nov 2019 20:13:45 GMT
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=8853F7D35B2A2695C5841E30373218C1.blade03_eu_a_api_d3_data; Path=/api/d3-data/; HttpOnly
Vary: Accept-Encoding
content-type: application/json;charset=UTF-8
content-encoding: gzip
content-length: 92
x-trace-traceid: 15c8652f-95b2-3c80-c512-fa165a04a81a
x-trace-spanid: 15c8652f-95b2-43b0-c512-fa165a04a81a
x-trace-parentspanid: 15c8652f-95b2-4380-c512-fa165a04a81a
x-frame-options: SAMEORIGIN
X-Content-Type-Options: nosniff
connection: keep-alive
{
“code”: “NOTFOUND”,
“reason”: “The requested data could not be found.”
}
And sometimes it also returns 200:
200 response
HTTP/1.1 200 OK
Date: Tue, 19 Nov 2019 20:13:49 GMT
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=B246B989EA5F4E62F976250891342817.blade08_eu_b_api_d3_data; Path=/api/d3-data/; HttpOnly
Vary: Accept-Encoding
content-type: application/json;charset=UTF-8
content-encoding: gzip
content-length: 664
x-trace-traceid: 15c865e7-bf08-f460-8521-fa165a196292
x-trace-spanid: 15c865e7-bf08-f5a0-8521-fa165a196292
x-trace-parentspanid: 15c865e7-bf08-f570-8521-fa165a196292
x-frame-options: SAMEORIGIN
X-Content-Type-Options: nosniff
connection: keep-alive
{
“id”: “Unique_Wand_006_x1”,
“slug”: “blackhand-key”,
“name”: “Blackhand Key”,
…
}
Sadly, from what I’ve seen so far, this could happen to any item at any time.