On Production, I seem to get errors on getEbayDetails when requesting pretty much any kind of details. This is true even when using the API Explorer and its 'Site Details' example on both the US and UK siteid, and using both our normal user account and my personal user account (via Auth'n'Auth tokens).
It works in Sandbox.
e.g. (using the API Explorer, Trading API, geteBayDetails, siteID 0, API 1349):
Headers
X-EBAY-API-SITEID:0
X-EBAY-API-COMPATIBILITY-LEVEL:1349
X-EBAY-API-CALL-NAME:GeteBayDetails
Call
<?xml version="1.0" encoding="utf-8"?>
<GeteBayDetailsRequest xmlns="urn: ebay :apis:eBLBaseComponents">
<RequesterCredentials>
<eBayAuthToken>REDACTED</eBayAuthToken>
</RequesterCredentials>
<ErrorLanguage>en_US</ErrorLanguage>
<WarningLevel>High</WarningLevel>
<DetailName>SiteDetails</DetailName>
</GeteBayDetailsRequest>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<GeteBayDetailsResponse
xmlns="urn: ebay :apis:eBLBaseComponents">
<Timestamp>2024-07-18T09:55:09.607Z</Timestamp>
<Ack>Failure</Ack>
<Errors>
<ShortMessage>Invalid meta field name SiteId or meta field SiteId not supported.</ShortMessage>
<LongMessage>You have entered a invalid Meta Field name SiteId, or meta field SiteId is not currently supported.</LongMessage>
<ErrorCode>12000</ErrorCode>
<SeverityCode>Error</SeverityCode>
<ErrorParameters ParamID="0">
<Value>SiteId</Value>
</ErrorParameters>
<ErrorClassification>RequestError</ErrorClassification>
</Errors>
<Version>1201</Version>
<Build>E1201_CORE_API6_19110890_R1</Build>
</GeteBayDetailsResponse>
Note that where the call and response had 'ebay' wrapped in colons, I had to put spaces around 'ebay' in the above bits to stop the forum's formatter mangling it.
I get something similar if I try different DetailName values e.g. ShippingCarrierDetails, CurrencyDetails, ShippingServiceDetails.
