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:SetStoreCategoriesResponseType"
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:TaskID?, ns:Status?, ns:CustomCategory?
</...>
All Direct / Indirect Based Elements (1):
ns:SetStoreCategoriesResponse
Known Usage Locations
Annotation
Base response of the SetStoreCategories call. Returns the status of the eBay Store category changes.
Type Definition Detail
Type Derivation Tree
ns:AbstractResponseType (extension)
  ns:SetStoreCategoriesResponseType
XML Source (w/o annotations (4); see within schema source)
<xs:complexType name="SetStoreCategoriesResponseType">
<xs:complexContent>
<xs:extension base="ns:AbstractResponseType">
<xs:sequence>
<xs:element minOccurs="0" name="TaskID" type="xs:long"/>
<xs:element minOccurs="0" name="Status" type="ns:TaskStatusCodeType"/>
<xs:element minOccurs="0" name="CustomCategory" type="ns:StoreCustomCategoryArrayType"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
Content Element Detail (all declarations defined in this component; 3/19)
ns:CustomCategory
Type:
ns:StoreCustomCategoryArrayType, complex content
Contains hierarchy data for eBay Store categories that you have created/modified.
Component Diagram
XML Representation Summary
<ns:CustomCategory>
   
Content: 
ns:CustomCategory*
</ns:CustomCategory>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="CustomCategory" type="ns:StoreCustomCategoryArrayType"/>
ns:Status
Type:
ns:TaskStatusCodeType, simple content
When an eBay Store category structure change is processed synchronously, the status is returned as 'Complete' or 'Failed'. For asynchronously processed changes, the status is reported as 'InProgress' or 'Pending'. Use GetStoreCategoryUpdateStatus to monitor the status of asynchronously processed changes.
XML Representation Summary
<ns:Status>
   
Content: 
{ enumeration of xs:token }
</ns:Status>
Simple Content
Enumeration:
"Pending"
 - 
(out) The category changes have not started.
"InProgress"
 - 
(out) The category changes are in progress.
"Complete"
 - 
(out) The category changes completed successfully.
"Failed"
 - 
(out) The category changes failed.
"CustomCode"
 - 
(out) Reserved for internal or future use.
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="Status" type="ns:TaskStatusCodeType"/>
ns:TaskID
Type:
xs:long, predefined, simple content
The task ID associated with the category structure change request. For a simple change, the SetStoreCategories call is processed synchronously. That is, simple changes are made immediately and then the response is returned. For synchronous processing, the task ID in the response is 0. If the category structure changes affect many listings, the changes will be processed asynchronously and the task ID will be a positive number. Use the non-zero task ID with GetStoreCategoryUpdateStatus to monitor the status of asynchronously processed changes.
XML Representation Summary
<ns:TaskID>
   
Content: 
{ xs:long }
</ns:TaskID>
XML Source (w/o annotations (1); see within schema source)
<xs:element minOccurs="0" name="TaskID" type="xs:long"/>
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.