getCompatibilitySearchDataVersion
Note: All calls in the Product Metadata API have been deprecated and will be decommissioned on April 27th, 2026. Current users of this API are recommended to migrate to the compatibilities methods of the Metadata API.
Use this call to find the version and update time for compatibility search metadata of the specified category. Separate version and update time information is maintained for search names and search values. Use this call to check for changes when you retrieve and store compatibility search metadata locally.
See Parts Compatibility for more information about the purpose of parts compatibility and how to use the API to include parts compatibility into your listings.
See also the reference documentation for these calls:
- getCompatibilitySearchNames - Returns all properties available for a given catalog enabled category.
- getCompatibilitySearchValues - Retrieves all available values and their dependencies for a given product property or a group of properties (of the product catalog).
- getCompatibilitySearchValuesBulk - Retrieves property values for multiple fields (up to 10).
Input
See also Samples.
The box below lists all fields that could be included in the call request. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).
<?xml version="1.0" encoding="utf-8"?> <getCompatibilitySearchDataVersionRequest xmlns="http://www.ebay.com/marketplace/marketplacecatalog/v1/services"> <!-- Call-specific Input Fields --> <categoryId> string </categoryId> </getCompatibilitySearchDataVersionRequest>
| Argument | Type | Occurrence | Meaning |
|---|
If a specified category ID doesn't match an existing category for the site, eBay returns an invalid-category error message. To determine valid categories, use the Trading API GetCategories call.
Max length: 10.
Output
See also Samples.
The box below lists all fields that might be returned in the response. To learn more about an individual field or its type, click its name in the box (or scroll down to find it in the table below the box).
<?xml version="1.0" encoding="utf-8"?> <getCompatibilitySearchDataVersionResponse xmlns="http://www.ebay.com/marketplace/marketplacecatalog/v1/services"> <!-- Call-specific Output Fields --> <namesDetails> VersionDetails <updateTime> dateTime </updateTime> <version> string </version> </namesDetails> <valueDetails> VersionDetails <updateTime> dateTime </updateTime> <version> string </version> </valueDetails> <!-- Standard Output Fields --> <ack> AckValue </ack> <errorMessage> ErrorMessage <error> ErrorData <category> ErrorCategory </category> <domain> string </domain> <errorId> long </errorId> <exceptionId> token </exceptionId> <message> string </message> <parameter name="string"> ErrorParameter (string) </parameter> <!-- ... more parameter values allowed here ... --> <severity> ErrorSeverity </severity> <subdomain> string </subdomain> </error> <!-- ... more error nodes allowed here ... --> </errorMessage> <timestamp> dateTime </timestamp> <version> string </version> </getCompatibilitySearchDataVersionResponse>
| Return Value | Type | Occurrence | Meaning |
|---|
Applicable values:
Code so that your app gracefully handles any future changes to this list.
repeatable: [0..*] Details about a single error.
Applicable values:
Code so that your app gracefully handles any future changes to this list.
- domain values:
- Marketplace
- A business or validation error occurred in the service.
- SOA
- An exception occurred in the Service Oriented Architecture (SOA) framework.
repeatable: [0..*] Various warning and error messages return one or more variables that contain contextual information about the error. This is often the field or value that triggered the error.
[ attribute name ] string Conditionally Various warning and error messages return one or more variables that contain contextual information about the error. This is often the field or value that triggered the error.
If the request fails and the application is the source of the error (for example, a required element is missing), update the application before you retry the request. If the problem is due to incorrect user data, alert the end-user to the problem and provide the means for them to correct the data. Once the problem in the application or data is resolved, re-send the request to eBay.
If the source of the problem is on eBay's side, you can retry the request a reasonable number of times (eBay recommends you try the request twice). If the error persists, contact Developer Technical Support. Once the problem has been resolved, you can resend the request in its original form.
If a warning occurs, warning information is returned in addition to the business data. Normally, you do not need to resend the request (as the original request was successful). However, depending on the cause of the warning, you might need to contact the end user, or eBay, to effect a long term solution to the problem.
Applicable values:
Code so that your app gracefully handles any future changes to this list.
- subdomain values:
- MarketplaceCatalog
- The error is specific to the Marketplace Catalog subdomain.
- MarketplaceCommon
- The error is common to all Marketplace services.
Note: The version in use is normally the latest release version, as specified in the release notes. Note that eBay releases the API to international sites about a week after the API version is released to the US site.
Samples
Code samples not yet added for this call's documentation.
Change History
| Change Date | Description |
|---|---|
| 1.1.0 3/3/2010 |
|