Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- 1487 is dated October 6, 2026. A missing list may reflect access or request conditions, not zero compatibility.
- Outside US/Canada, lists return only to the listing seller or authorized callers on their behalf. Other callers' true setting is ignored.
- IncludeItemCompatibilityList defaults to false. Existing lists do not automatically return details; assess count-field conditions separately.
- Seller-entered lists and eBay catalog compatibility use different paths. Identify the source before diagnosis.
A missing list does not mean the part fits no vehicles
If synchronization loses Item.ItemCompatibilityList, record list not obtained rather than no compatible vehicles. An absent field and a truly empty list differ.
eBay's October 6, 2026 Trading API 1487 notes change access to this container. Reading conditions changed; this does not establish deletion of existing listing compatibility.
Check marketplace and caller first, whether details were requested second, and manual versus catalog source last. Then decide whether authorization, parameters, or the reading path needs adjustment.
Who can read lists outside US and Canada?
Outside those marketplaces, Item.ItemCompatibilityList returns only to the seller or users authorized to call GetItem on their behalf. IncludeItemCompatibilityList=true is ignored for other callers.
The rule concerns eBay marketplace and caller identity, not the operator's country. Being in the US or using Canadian egress does not replace marketplace and authorization checks or establish an exception.
Check whose identity the call uses and whether they represent the listing seller. An application's ability to send a request differs from seller authorization. Do not ask sellers to publish passwords or access tokens for diagnosis.
Why true still may not return details
IncludeItemCompatibilityList defaults to false. Explicit true requests details, but a list must exist and current access requirements must be satisfied. The flag cannot supply missing authorization or nonexistent data.
The reference says an existing list with false/omitted flag does not return details but returns Item.ItemCompatibilityCount. This is a count, not vehicle names, attributes, or notes.
Do not extend that condition into every unauthorized request receiving a count. For ignored true settings, record actual missing fields without promising count, a specific HTTP status, or a special error code.
Manual lists and catalog products use different paths
ItemCompatibilityList covers seller-manually-specified details, not compatibility associated with eBay catalog products. Inspecting only this container may target the wrong source.
Check whether the listing uses a catalog product. Its compatibility points to Metadata API getProductCompatibilities; manual lists continue through GetItem's parameters and access rules.
The paths are not interchangeable. Catalog compatibility is not a copy of every listing's manual list. Check method support and required information before switching; a method name does not establish integration or complete data access.
Do not replace missing data with an empty list
Record obtained details, count only, and unavailable data separately. Preserve previous records and current check state when fields are missing, resolving cause before updates instead of clearing relationships after one read.
Hypothetically, a tool reads German parts listings through a user not authorized for the seller. The list is absent despite true. Check authorization rather than deleting vehicles, retrying endlessly, or declaring incompatibility.
If the data is catalog-based, inspect the documented catalog path too. This example explains sequence, not measured results; actual cause needs listing, identity, and full response.
Verify the same conditions after adjustment
In your authorized environment, select a few listings with known sources and record marketplace, user, flag, and returned container. Hold conditions constant to separate access, parameter, and listing-data differences.
For details, verify each relationship is handled. For counts, do not display a full vehicle table. For absent fields, ensure downstream logic does not infer zero compatibility. Verify meaning, not merely a received response.
1487 does not identify older versions or network changes as access-restoration methods. If verified conditions still cannot explain results, contact support with request conditions excluding credentials and private information instead of repeatedly treating access changes as networking.
Sources
Frequently Asked Questions
Can anyone get all data in US/Canada?
No. Those marketplaces are exceptions to this added access restriction, not guarantees. Parameters, existing lists, and manual/catalog distinctions still apply.
Must sellers re-enter all parts listings?
The notes change read access, not require universal re-entry. Check source data and call conditions before bulk modification or clearing.
Can ItemCompatibilityCount prove one vehicle fits?
No. It gives a number, not the target vehicle's attributes or notes. Obtain corresponding details and verify the part and vehicle conditions.