| POST | /Catalog_Get |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| 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 |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| mode | form | string | No | |
| name | form | string | No | |
| operation | form | string | No | |
| value | form | string | No | |
| group | form | string | No |
| contact | |
| myContacts | |
| publicContacts | |
| allContacts |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
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/json
Content-Type: application/json
Content-Length: length
{"contact":"String","limit":0,"nom":0,"filters":[{"mode":"String","name":"String","operation":"String","value":"String","group":"String"}],"fields":["String"],"properties":["String"],"search_mode":"contact","search_phrase":"String"}