POST,GET | /audit/emailer/{userId} |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
userId | path | string | No | |
CreatedDate | body | DateTime | No | |
LessThan | body | bool | No | |
count | body | int | No | |
companyId | body | Guid | No | |
emailInfo | body | TypeEmailLog | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
emailBody | form | string | No | |
emailFrom | form | string | No | |
emailTo | form | string | No | |
emailCC | form | string | No | |
emailBCC | form | string | No | |
emailSubject | form | string | 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 /audit/emailer/{userId} HTTP/1.1
Host: n3tapi.palmettovdc.com
Accept: application/json
Content-Type: application/json
Content-Length: length
{"userId":"String","createdDate":"\/Date(-62135596800000-0000)\/","lessThan":false,"count":0,"companyId":"00000000000000000000000000000000","emailInfo":{"emailBody":"String","emailFrom":"String","emailTo":"String","emailCC":"String","emailBCC":"String","emailSubject":"String"}}