| All Verbs | /Gemifin/PriceList |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Token | query | string | No | |
| UserId | query | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Data | form | GemifinPriceListGpDto[] | No | |
| Error | form | bool | No | |
| ErrorMessage | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Eyes | form | Eyes | No | |
| LensType | form | int | No | |
| PriceExpectation | form | decimal | No | |
| AcceptancePayment | form | decimal | No | |
| SlipAmount | form | decimal | No | |
| RefundAmount | form | decimal | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UID | form | int | 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.
POST /json/reply/GemifinPriceListRequest HTTP/1.1
Host: data.oriem.cz
Content-Type: application/json
Content-Length: length
{"Token":"String","UserId":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Data":[{"Eyes":"OneEye","LensType":0,"PriceExpectation":0,"AcceptancePayment":0,"SlipAmount":0,"RefundAmount":0,"UID":0}],"Error":false,"ErrorMessage":"String"}