The [result] key of response of contentMetadataLookupUrl may be empty.

When using contentMetadataLookupUrl to get information for a custom B2B app, the [result] key may be empty.

Request


API: https://uclient-api.itunes.apple.com/WebObjects/MZStorePlatform.woa/wa/lookup?version=2&id=1481545259&p=mdm-lockup&caller=MDM&platform=enterprisestore&cc=jp&l=j

Code Block
header: {
"Content-type": "application/json",
"Cookie': 'itvt=***"
}


Response

Code Block
{
"results":{
★★★empty!★★★
},
"version":2,
"isAuthenticated":false,
"meta":{
"storefront":{
"id":"143462",
"cc":"JP"
},
"language":{
"tag":"ja-jp"
}
}
}


In some cases, the [result] key can be obtained correctly even in the same app.

Is anyone experiencing the same phenomenon?
Do you know why you can and may not get it?
I have noticed the same. I reported it using feedback assistant but nothing. I found out (by looking at HTTP headers) that some servers returned the info and some servers didn't, requests being sent within few minutes.
The [result] key of response of contentMetadataLookupUrl may be empty.
 
 
Q