TeleportService

Catalog_Init

The following routes are available for this service:
POST	/Catalog_Init

**Catalog_Init** Parameters:
Name	Parameter	Data Type	Required
contact	body	string	No
offers	body	OffersGet	No
get_categories	body	bool	No
get_filters	body	bool	No
get_total_quantity	body	bool	No
items	body	ItemsGet	No
evotor_shop_uuid	body	string	No

**OffersGet** Parameters:
Name	Parameter	Data Type	Required
action	form	bool	No
novetly	form	bool	No
popular	form	bool	No
quantity	form	int	No
fields	form	List<string>	No

**ItemsGet** Parameters:
Name	Parameter	Data Type	Required	Description
quantity	form	int	No
fields	form	List<string>	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /Catalog_Init HTTP/1.1 
Host: wbs.e-teleport.ru 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<Catalog_Init xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TeleportService.ServiceModel">
  <contact>String</contact>
  <evotor_shop_uuid>String</evotor_shop_uuid>
  <get_categories>false</get_categories>
  <get_filters>false</get_filters>
  <get_total_quantity>false</get_total_quantity>
  <items>
    <fields xmlns:d3p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
      <d3p1:string>String</d3p1:string>
    </fields>
    <quantity>0</quantity>
  </items>
  <offers>
    <action>false</action>
    <fields xmlns:d3p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
      <d3p1:string>String</d3p1:string>
    </fields>
    <novetly>false</novetly>
    <popular>false</popular>
    <quantity>0</quantity>
  </offers>
</Catalog_Init>