Management Information Web Service

LogSingleEventMultipleParams

The following routes are available for this service:
POST	/LogSingleEventMultipleParams

**LogSingleEventMultipleParams** Parameters:
Name	Parameter	Data Type	Required
SourceKey	body	string	No
TypeKey	body	string	No
EventParameters	body	List<EventParameter>	No
CSR	body	int?	No
PeriodStartDateTime	body	DateTime?	No
PeriodEndDateTime	body	DateTime?	No
GroupingGUID	body	Guid?	No
EventVerified	body	bool?	No

**EventParameter** Parameters:
Name	Parameter	Data Type	Required
ParameterKey	body	string	No
EventValue	body	string	No
GroupingName	body	string	No
GroupingCount	body	int?	No

**GenericRequestResult** Parameters:
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

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /json/reply/LogSingleEventMultipleParams HTTP/1.1 
Host: mi-ws-test.worldpay.com 
Content-Type: application/json
Content-Length: length

{"SourceKey":"String","TypeKey":"String","EventParameters":[{"ParameterKey":"String","EventValue":"String","GroupingName":"String","GroupingCount":0}],"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"}