502 Internal server error "/v1/tracks?ids="

Hi! For a few hours, we have been getting a lot of 502 “Internal server error” returned by the API on the endpoint to retrieve tracks details “/v1/tracks?ids=”. It is the same for the “album” endpoints to retrieve details of multiple album IDs.

Do you have some updates related to this? Temporary down?

Hi Thomas,

we can’t reproduce your issue - can you provide us with full response headers and body (including internal error code and reference) you are receiving from the API?

Hi!
Sure, here is an example (with the correct authentication done):
GET https://api.music.amazon.dev/v1/tracks?ids=B0B2Y4Q5LR,B0B2NFT8CW,B0B554851T,B0B4YTS5QN,B0B5VNMY3K,B07Y6TCBTG,B0B81M5441,B09QFLCG45,B0BH6Q1BFM,B0BC6KNWVV,B0BD4SYMSS,B09YQFW72D,B09JDWMS4L,B0B3S52MB5,B09QFPDCD5,B0B6WRSGDS,B0BH6XRZ6Q,B0B3M7YNW9,B0B2HXN1ZR,B0B3585Q6X,B09ZP617VN,B0BHJF837T,B0B4ZCB6DY,B0BYYX7Z9B,B0BKL1R4NN,B09SVGCBGK,B0C9MFXLH9,B0BFCX4JTV,B09W4567C3,B09XJ9DL4B,B09QNCZ9KF,B09JK8K6JW,B09MYDMYZV,B0B5LWHBYN,B09XJ89L64,B09RGK135R,B09TPSRL69,B09TDH99RJ,B09QMQ9WKV,B09YGBXPG6,B09Z5XB15S,B09BC94JHL,B0BKR2XJJD,B0B2NNJZVG,B0BB6L6TP3,B09HMW4YSC,B09PTR4KD9,B0BKH66516,B0B344W2D7,B0B1X7DST3

Is returning:
[“HTTP/2 502 \r\n”,“date: Fri, 26 Apr 2024 13:20:47 GMT\r\n”,“content-type: application/json; charset=utf-8\r\n”,“content-length: 47\r\n”,“x-amzn-requestid: 3f612d66-4f8f-4fb2-884c-235a2ad24896\r\n”,“access-control-allow-origin: *\r\n”,“x-amz-apigw-id: W1eGqFPOIAMEo3w=\r\n”,“x-amzn-trace-id: Root=1-662baa2a-1e0c42e80eaecb1f34d126d7\r\n”,“access-control-allow-credentials: true\r\n”,“HTTP/2 502 \r\n”,“date: Fri, 26 Apr 2024 13:20:54 GMT\r\n”,“content-type: application/json; charset=utf-8\r\n”,“content-length: 47\r\n”,“x-amzn-requestid: caa81efe-b6bf-4af1-a2fc-21f2fafe4724\r\n”,“access-control-allow-origin: *\r\n”,“x-amz-apigw-id: W1eHsEw-IAMEv9A=\r\n”,“x-amzn-trace-id: Root=1-662baa30-6d6ac9f34cc64da072f3ea53\r\n”,“access-control-allow-credentials: true\r\n”,“HTTP/2 502 \r\n”,“date: Fri, 26 Apr 2024 13:21:02 GMT\r\n”,“content-type: application/json; charset=utf-8\r\n”,“content-length: 47\r\n”,“x-amzn-requestid: b4845737-62a2-4241-ae34-ee2ebe7daf47\r\n”,“access-control-allow-origin: *\r\n”,“x-amz-apigw-id: W1eI9GmYIAMEp1w=\r\n”,“x-amzn-trace-id: Root=1-662baa39-0f3544f7276109255419544e\r\n”,“access-control-allow-credentials: true\r\n”]
Response body:

{"data":null,"message":"Internal server error"}"

I have many more “x-amzn-requestid” or “x-amzn-trace-id” if you need them.

UPDATE: It seems to only send 20 IDs instead of 50 or more is working. But your documentation indicates that we can send up to 100 IDs…

Thank you Thomas for reporting this issue. The response headers are very helpful - I can trace the issue back to one of our upstream services.
I can no longer trigger the issue, even with 100 trackIds as input, so I suspect an intermittent problem. We’ll continue to investigate.

1 Like

Ok, thank you for the update and investigation!

Hi!
I’m getting this error again while trying to retrieve 20 albums with IDs. See attached headers:

[“HTTP/2 502 \r\n”,“date: Fri, 03 May 2024 08:23:25 GMT\r\n”,“content-type: application/json; charset=utf-8\r\n”,“content-length: 47\r\n”,“x-amzn-requestid: 71d0683c-ce71-46db-b998-86ae27c01157\r\n”,“access-control-allow-origin: *\r\n”,“x-amz-apigw-id: XL3G0HsFoAMEfQA=\r\n”,“x-amzn-trace-id: Root=1-66349ef8-2e7c04ca32591d851886599a\r\n”,“access-control-allow-credentials: true\r\n”,“HTTP/2 502 \r\n”,“date: Fri, 03 May 2024 08:23:32 GMT\r\n”,“content-type: application/json; charset=utf-8\r\n”,“content-length: 47\r\n”,“x-amzn-requestid: 19ae19a5-597f-4931-8118-8e4337e8ff2c\r\n”,“access-control-allow-origin: *\r\n”,“x-amz-apigw-id: XL3H7GMWoAMEHKw=\r\n”,“x-amzn-trace-id: Root=1-66349eff-3830c4c6298888286f50e54d\r\n”,“access-control-allow-credentials: true\r\n”,“HTTP/2 502 \r\n”,“date: Fri, 03 May 2024 08:23:41 GMT\r\n”,“content-type: application/json; charset=utf-8\r\n”,“content-length: 47\r\n”,“x-amzn-requestid: a7f7bc36-d2af-4138-9efc-07d35446e99d\r\n”,“access-control-allow-origin: *\r\n”,“x-amz-apigw-id: XL3JWGU5IAMEjcw=\r\n”,“x-amzn-trace-id: Root=1-66349f08-61bce7db27346a5943da48d9\r\n”,“access-control-allow-credentials: true\r\n”]

Is it possible a specific “id” in the list is causing the issue?
Here is the list: “B00EWCB34Y,B078X6J5DN,B01DGIW96A,B07JHNQFGC,B0761RNZJN,B014AU53AM,B0138CL9OM,B00KJX871M,B00BOWA74W,B008LPKNT4,B0779LQW7Z,B07JHHQBVM,B07DJ7ZHSS,B012C4OVQU,B00AXOIGKE,B09RPMZ6H9,B01KQ43B7I,B01DAKM5NG,B078T1VJ77,B0092JAA4Q”