| All Verbs | /SendEmail |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Token | query | string | No | |
| UserId | query | int | No | |
| Sender | query | string | No | |
| SenderName | query | string | No | |
| To | query | string | No | |
| Subject | query | string | No | |
| Body | query | string | No | |
| ReferenceUID | query | int | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Error | form | bool | No | |
| ErrorMessage | 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 /json/reply/SendEmail HTTP/1.1
Host: data.oriem.cz
Content-Type: application/json
Content-Length: length
{"Token":"String","UserId":0,"Sender":"String","SenderName":"String","To":"String","Subject":"String","Body":"String","ReferenceUID":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"Error":false,"ErrorMessage":"String"}