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 /listmerge/changelog/unused HTTP/1.1
Host: hcbtas-q-albamfs-api.azurewebsites.net
Accept: application/json
Content-Type: application/json
Content-Length: length
{"changeLogs":[{"referenceId":"String","country":"String","language":"String","section":"String","itemCode":"String","itemId":"String","history":[{"updatedBy":"String","dateCreated":"0001-01-01T00:00:00.0000000","element":"String","old":"String","new":"String","status":"String","approvedBy":"String","dateApproved":"0001-01-01T00:00:00.0000000"}],"id":"String"}]}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"referenceId":"String","country":"String","language":"String","section":"String","itemCode":"String","itemId":"String","history":[{"updatedBy":"String","dateCreated":"0001-01-01T00:00:00.0000000","element":"String","old":"String","new":"String","status":"String","approvedBy":"String","dateApproved":"0001-01-01T00:00:00.0000000"}],"id":"String"}