POST | /adjustments/awardsales/{BeeNumber} |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
BeeNumber | path | decimal? | No | |
AdjustmentAmount | body | decimal? | No | |
AdjustmentDate | body | DateTime? | No | |
Campaign | body | string | No | |
RequesterName | body | string | No | |
ProcessId | body | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
CstCampaignSalesAdjustmentGuid | form | decimal | 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.
POST /adjustments/awardsales/{BeeNumber} HTTP/1.1
Host: extensions.avon.ca
Accept: application/json
Content-Type: application/json
Content-Length: length
{"beeNumber":0,"adjustmentAmount":0,"adjustmentDate":"0001-01-01T00:00:00.0000000","campaign":"String","requesterName":"String","processId":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"cstCampaignSalesAdjustmentGuid":0,"responseStatus":{"errorCode":"String","message":"String","stackTrace":"String","errors":[{"errorCode":"String","fieldName":"String","message":"String","meta":{"String":"String"}}],"meta":{"String":"String"}}}