TeleportService

Catalog_Get

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

**Catalog_Get** Parameters:
Name	Parameter	Data Type	Required
contact	body	string	No
limit	body	int	No
nom	body	int	No
filters	body	List<CatalogFilter>	No
fields	body	List<string>	No
properties	body	List<string>	No
search_mode	body	SearchMode	No
search_phrase	body	string	No

**CatalogFilter** Parameters:
Name	Parameter	Data Type	Required
mode	form	string	No
name	form	string	No
operation	form	string	No
value	form	string	No
group	form	string	No

**SearchMode** Enum:
contact
myContacts
publicContacts
allContacts

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_Get HTTP/1.1 
Host: wbs.e-teleport.ru 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<Catalog_Get xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TeleportService.ServiceModel">
  <contact>String</contact>
  <fields xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
    <d2p1:string>String</d2p1:string>
  </fields>
  <filters>
    <CatalogFilter>
      <group>String</group>
      <mode>String</mode>
      <name>String</name>
      <operation>String</operation>
      <value>String</value>
    </CatalogFilter>
  </filters>
  <limit>0</limit>
  <nom>0</nom>
  <properties xmlns:d2p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
    <d2p1:string>String</d2p1:string>
  </properties>
  <search_mode>contact</search_mode>
  <search_phrase>String</search_phrase>
</Catalog_Get>