| POST | /Mail/Status |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Signature | body | Object | No | |
| EventData | body | MailGunResponse | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Message | form | MessageResponseContent | No | |
| Event | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Headers | form | HeaderResponseContent | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| To | form | string | No | |
| MessageId | form | string | No | |
| From | form | string | No | |
| Subject | 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 /Mail/Status HTTP/1.1
Host: communicationhub.carelogic-cloud.de
Accept: application/json
Content-Type: application/json
Content-Length: length
{"Signature":{},"event-data":{"Message":{"Headers":{"To":"String","message-id":"String","From":"String","Subject":"String"}},"Event":"String"}}
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length false