| GET | /search | ||
|---|---|---|---|
| GET | /{Ver}/search |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Q | query | string | No | |
| TokenId | query | Guid | No | |
| Ver | path | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| Result | form | ProductModel[] | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | Guid | No | |
| ManufacturerTitle | form | string | No | |
| Number | form | string | No | |
| Title | form | string | No |
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.
GET /search HTTP/1.1 Host: api.oszz.ru Accept: application/json
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}},"result":[{"id":"00000000000000000000000000000000","manufacturerTitle":"String","number":"String","title":"String"}]}