| PUT | /licenses_transactions/{Id} |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | path | long | Yes | |
| AppUserId | body | long | Yes | |
| LicensesId | body | long | Yes | |
| PaidAmount | body | double | Yes | |
| PaidDate | body | DateTime | Yes | |
| FromDate | body | DateTime | Yes | |
| ToDate | body | DateTime | Yes | |
| Reference | body | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Id | form | long | No | |
| AppUserId | form | long | No | |
| LicensesId | form | long | No | |
| PaidAmount | form | double | No | |
| PaidDate | form | DateTime | No | |
| FromDate | form | DateTime | No | |
| ToDate | form | DateTime | No | |
| Reference | form | string | No | |
| ResponseStatus | form | ResponseStatus | 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 /licenses_transactions/{Id} HTTP/1.1
Host: api.sfgtec.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"id":0,"appUserId":0,"licensesId":0,"paidAmount":0,"paidDate":"\/Date(-62135596800000-0000)\/","fromDate":"\/Date(-62135596800000-0000)\/","toDate":"\/Date(-62135596800000-0000)\/","reference":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"id":0,"appUserId":0,"licensesId":0,"paidAmount":0,"paidDate":"\/Date(-62135596800000-0000)\/","fromDate":"\/Date(-62135596800000-0000)\/","toDate":"\/Date(-62135596800000-0000)\/","reference":"String","responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}