TeleportService

Basket_AddItem

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

**Basket_AddItem** Parameters:
Name	Parameter	Data Type	Required
contact	body	string	No
item_id	body	string	No
quantity	body	decimal	No
set_mode	body	bool	No
price	body	decimal	No
basketType	body	BasketTypes	No

**BasketTypes** Enum:
orders
returns

**BasketAddItemResponse** Parameters:
Name	Parameter	Data Type	Required	Description
errCode	form	int	No
retVal	form	Basket	No

**Basket** Parameters:
Name	Parameter	Data Type	Required
id	form	int	No
user_name	form	string	No
contact	form	string	No
item_id	form	string	No
article	form	string	No
name	form	string	No
quantity	form	decimal	No
price	form	decimal	No
sum	form	decimal	No
basketType	form	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 /Basket_AddItem HTTP/1.1 
Host: wbs.e-teleport.ru 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<Basket_AddItem xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TeleportService.ServiceModel">
  <basketType>orders</basketType>
  <contact>String</contact>
  <item_id>String</item_id>
  <price>0</price>
  <quantity>0</quantity>
  <set_mode>false</set_mode>
</Basket_AddItem>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<BasketAddItemResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TeleportService.ServiceModel">
  <errCode>0</errCode>
  <retVal>
    <article>String</article>
    <basketType>String</basketType>
    <contact>String</contact>
    <id>0</id>
    <item_id>String</item_id>
    <name>String</name>
    <price>0</price>
    <quantity>0</quantity>
    <sum>0</sum>
    <user_name>String</user_name>
  </retVal>
</BasketAddItemResponse>