| PUT | /POS/Pharma/Prescriptions/Used |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| PrescriptionNumber | body | string | No | |
| Quantity | body | decimal | No | |
| ProdId | body | string | No | |
| SaleId | body | Guid | No | |
| ReceiverId | body | string | No | |
| CofoundingProviderId | body | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| UsedPresecriptionId | 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.
PUT /POS/Pharma/Prescriptions/Used HTTP/1.1
Host: 10.10.0.107
Accept: application/json
Content-Type: application/json
Content-Length: length
{"PrescriptionNumber":"String","Quantity":0,"ProdId":"String","SaleId":"00000000000000000000000000000000","ReceiverId":"String","CofoundingProviderId":"String"}
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"}},"UsedPresecriptionId":"String"}