POST | /api/SalesForce/Event |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ClassName | body | string | No | |
UniqueId | body | string | No | |
CreatedDateTime | body | DateTime | No | |
ClientId | body | int | No | |
GroupId | body | string | No | |
EventName | body | string | No | |
EventDescription | body | string | No | |
Region | body | string | No | |
CostCenter | body | string | No | |
RegionCostCenter | body | string | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ClassName | form | string | No | |
UniqueId | form | string | No | |
CreatedDateTime | form | DateTime | No | |
ClientId | form | int | No | |
BillhighwaycampaignId | form | string | No | |
ErrorCode | form | int | No | |
ErrorMessage | form | string | No | |
IsError | form | bool | 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 /api/SalesForce/Event HTTP/1.1
Host: devapi.billhighway.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"ClassName":"String","UniqueId":"String","CreatedDateTime":"0001-01-01T00:00:00.0000000","ClientId":0,"GroupId":"String","EventName":"String","EventDescription":"String","Region":"String","CostCenter":"String","RegionCostCenter":"String"}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length {"ClassName":"String","UniqueId":"String","CreatedDateTime":"0001-01-01T00:00:00.0000000","ClientId":0,"BillhighwaycampaignId":"String","ErrorCode":0,"ErrorMessage":"String","IsError":false}