Overview 
Namespace 
WSDL 
Schema 
 Component 
Index 
PREV C-TYPE   NEXT C-TYPE
FRAMES   NO FRAMES NS-Bindings
SUMMARY: XML REP | DERIVED | USE
DETAIL: DESC | XML SRC | TYPE | ATTR | CHILD
eBay Trading API
complexType "ns:GetCategorySpecificsResponseType"
Namespace:
urn:ebay:apis:eBLBaseComponents
Content:
complex, 18 elements, elem. wildcard
Defined:
globally in Schema in ebaySvc.wsdl; see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
Component Diagram
XML Representation Summary
<...>
   
Content: 
ns:Timestamp?, ns:Ack?, ns:CorrelationID?, ns:Errors*, ns:Message?, ns:Version?, ns:Build?, ns:NotificationEventName?, ns:DuplicateInvocationDetails?, ns:RecipientUserID?, ns:EIASToken?, ns:NotificationSignature?, ns:HardExpirationWarning?, ns:BotBlock?, ns:ExternalUserData?, {any}*, ns:Recommendations*, ns:TaskReferenceID?, ns:FileReferenceID?
</...>
All Direct / Indirect Based Elements (1):
ns:GetCategorySpecificsResponse
Known Usage Locations
Annotation
This is the base response type for the GetCategorySpecifics call. This call retrieves recommended Item Specifics names and values for one or multiple eBay Categories.
Type Definition Detail
Type Derivation Tree
ns:AbstractResponseType (extension)
  ns:GetCategorySpecificsResponseType
XML Source (w/o annotations (4); see within schema source)
<xs:complexType name="GetCategorySpecificsResponseType">
<xs:complexContent>
<xs:extension base="ns:AbstractResponseType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="Recommendations" type="ns:RecommendationsType"/>
<xs:element minOccurs="0" name="TaskReferenceID" type="xs:string"/>
<xs:element minOccurs="0" name="FileReferenceID" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
Content Element Detail (all declarations defined in this component; 3/19)
ns:FileReferenceID
Type:
xs:string, predefined, simple content
A TaskReferenceID and a FileReferenceID value are returned if the CategorySpecificsFileInfo field is included in the call request and set to true. These values will be used as inputs in the downloadFile call of the File Transfer API. That API lets you retrieve a single (bulk) GetCategorySpecifics response with all the Item Specifics recommendations available for the requested site ID. (The downloadFile call downloads a .zip file as an attachment.)
XML Representation Summary
<ns:FileReferenceID>
   
Content: 
{ xs:string }
</ns:FileReferenceID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="FileReferenceID" type="xs:string"/>
ns:Recommendations
Type:
ns:RecommendationsType, complex content
This container provide details about relevant Item Specifics for the specified category. Required Item Specifics are generally returned at the top of the response payload, followed by the other most common/popular Item Specifics for the category. If an Item Specific is required, a MinValues field will be returned with a value of 1, and the corresponding UsageConstraint field will show a value of Required. Optional Item Specifics are returned after required and recommended Item Specifics, but sellers should still provide any optional Item Specific name-value pairs if known and relevant for the product.

As mentioned above, the most relevant Item Specifics are returned first, and similarly, if an Item Specific has multiple suggested values, these values are sorted according to popularity (most popular to less popular/common).

This node returns empty (or it's not returned) for a category if there is no applicable data (such as when you request a parent category, a category that has no popular Item Specifics yet, or a duplicate category that was already returned). If you pass in the CategoryID and Name fields together, but no matching values are found for the name, eBay returns the name with no values (even if the name is not recommended).

If GetCategoryFeatures indicates that Item Specifics are enabled for a leaf category, but GetCategorySpecifics doesn't return any recommendations for that category, the seller can still specify their own Item Specifics in that category.
Component Diagram
XML Representation Summary
<ns:Recommendations>
   
Content: 
ns:CategoryID?, ns:ProductIdentifiers*, ns:NameRecommendation*, ns:Updated?, {any}*
</ns:Recommendations>
XML Source (w/o annotations (1); see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="Recommendations" type="ns:RecommendationsType"/>
ns:TaskReferenceID
Type:
xs:string, predefined, simple content
A TaskReferenceID and a FileReferenceID value are returned if the CategorySpecificsFileInfo field is included in the call request and set to true. These values will be used as inputs in the downloadFile call of the File Transfer API. That API lets you retrieve a single (bulk) GetCategorySpecifics response with all the Item Specifics recommendations available for the requested site ID. (The downloadFile call downloads a .zip file as an attachment.)
XML Representation Summary
<ns:TaskReferenceID>
   
Content: 
{ xs:string }
</ns:TaskReferenceID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="TaskReferenceID" type="xs:string"/>
Overview 
Namespace 
WSDL 
Schema 
 Component 
Index 
PREV C-TYPE   NEXT C-TYPE
FRAMES   NO FRAMES NS-Bindings
SUMMARY: XML REP | DERIVED | USE
DETAIL: DESC | XML SRC | TYPE | ATTR | CHILD
eBay Trading API
WSDL documentation generated with FlexDoc/XML 1.13 using FlexDoc/XML WSDLDoc 1.2.5 template set. All XSD diagrams generated by FlexDoc/XML DiagramKit.