Component 
SUMMARY: XML REP | DERIVED | USE
DETAIL: DESC | XML SRC | TYPE | ATTR | CHILD
eBay Trading API

complexType "ns:CategoryItemSpecificsType"
Namespace:
Content:
complex, 2 elements, elem. wildcard
Defined:
globally in Schema in ebaySvc.wsdl; see XML source
Includes:
definitions of 2 elements, elem. wildcard
Used:
Component Diagram
XML Representation Summary
<...>
   
Content: 
</...>
All Direct / Indirect Based Elements (1):
Known Usage Locations
Annotation
This type is used by the CategorySpecific container in the GetCategorySpecifics request. The CategorySpecific container is used when a seller wants to pass in Item Specific name-value(s) pairs for a specific category to discover if eBay has better name or value recommendations for that Item Specific.
XML Source (w/o annotations (3); see within schema source)
<xs:complexType name="CategoryItemSpecificsType">
<xs:sequence>
<xs:element minOccurs="0" name="CategoryID" type="xs:string"/>
<xs:element minOccurs="0" name="ItemSpecifics" type="ns:NameValueListArrayType"/>
<xs:any maxOccurs="unbounded" minOccurs="0" processContents="lax"/>
</xs:sequence>
</xs:complexType>
Content Element Detail (all declarations defined in this component; 3/3)
ns:CategoryID
Type:
xs:string, predefined, simple content
An eBay category ID is passed into this field to identify the eBay category for which the seller is providing Item Specific name-value(s) pairs. Multiple CategoryID fields can be passed in if the Item Specific name-value(s) pairs are applicable for multiple categories. However, more categories can result in longer call response times. If your request times out, specify fewer category IDs.

Note: The call request requires either one or more CategoryID values (at the root level), one or more CategorySpecific.CategoryID values, or the CategorySpecificsFileInfo boolean field. The CategorySpecificsFileInfo field is only used if the user plans to use the downloadFile call of the FileTransfer API to retrieve Item Specifics. CategoryID and CategorySpecific.CategoryID can both be used in the same call request.
XML Representation Summary
<ns:CategoryID>
   
Content: 
{ xs:string }
</ns:CategoryID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="CategoryID" type="xs:string"/>

ns:ItemSpecifics
Type:
ns:NameValueListArrayType, complex content
This container is used to input Item Specific name-value(s) pairs for a specific category to discover if eBay has better name or value recommendations for that Item Specific. The Item Specific name can be an arbitrary name that the user wants to check, or it could be a name that was returned in a prior GetCategorySpecifics response. At least one NameValueList container must be used if the CategorySpecific container is used.
Component Diagram
XML Representation Summary
<ns:ItemSpecifics>
   
Content: 
</ns:ItemSpecifics>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="ItemSpecifics" type="ns:NameValueListArrayType"/>

{any element from any namespace}
XML Source (see within schema source)
<xs:any maxOccurs="unbounded" minOccurs="0" processContents="lax"/>

 Component 
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.