| POST | /LogSingleEventSingleParam |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| SourceKey | body | string | No | |
| TypeKey | body | string | No | |
| SingleParameterKey | body | string | No | |
| SingleEventValue | body | string | No | |
| CSR | body | int? | No | |
| PeriodStartDateTime | body | DateTime? | No | |
| PeriodEndDateTime | body | DateTime? | No | |
| GroupingGUID | body | Guid? | No | |
| EventVerified | body | bool? | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Successful | body | bool | Yes | Result success flag (true/false) |
| Message | body | string | No | Result message (reason for fail) |
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/LogSingleEventSingleParam HTTP/1.1
Host: mi-ws-test.worldpay.com
Content-Type: application/json
Content-Length: length
{"SourceKey":"String","TypeKey":"String","SingleParameterKey":"String","SingleEventValue":"String","CSR":0,"PeriodStartDateTime":"\/Date(-62135596800000-0000)\/","PeriodEndDateTime":"\/Date(-62135596800000-0000)\/","GroupingGUID":"00000000000000000000000000000000","EventVerified":false}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Successful":false,"Message":"String"}