received_email
A message was delivered to an address.
| Sent with | server, platform keys (see write keys) |
| Mode | strict: exactly the declared fields; an undeclared key, a wrong type or a missing required key quarantines the event |
| Version | 1 (_schema_version on the stored row) |
| State | active |
| Required fields | none |
| Revenue | none: the revenue block is refused |
| Identity evidence | none |
| Before consent | no |
Fields
The activity's own fields, sent as features. Identifier and attribute fields are moved out of features by the processor; see identifiers and attributes.
| Field | Type | Required | What happens to it | Meaning |
|---|---|---|---|---|
campaign_id | string | no, may be null | stays in features | The mail campaign the message belongs to. |
journey_id | string | no, may be null | stays in features | The automation journey the message was sent from, if any. |
list | string | no, may be null | stays in features | The mailing list the message or the subscription concerns. |
message_id | string | no, may be null | stays in features | The sent message, as the mail platform identifies it: the same value on received, opened, clicked and bounced. |
step_id | string | no, may be null | stays in features | The step within the journey. |
Example
One activity in a batch to POST /v1/activities, with debug so the answer says what the processor made of it. The envelope page explains every top-level field.
{
"batch": [
{
"activity_id": "0192f1a4-3db1-7ebb-8000-3db1ebbe0000",
"activity": "received_email",
"ts": "2026-10-17T20:00:00+02:00",
"owner_ref": "own:own_01M4XX0033FV7QXDRB5BQBRPGR",
"identifiers": [
{
"type": "email",
"value": "ana@example.com"
}
],
"features": {
"campaign_id": "cmp_summer_2027",
"journey_id": null,
"list": "summer-fest-2027",
"message_id": "msg_01M4XVBYC3FGXCPFRZEPGV20RZ",
"step_id": null
}
}
],
"debug": true
}
Try it
Sends this request from your browser. The key and the endpoint are kept in this browser only.
Versions
| Version | Mode | Key classes | Change |
|---|---|---|---|
| 1 (current) | strict | server, platform | first version |
A published version never changes; a change is a new version, and every stored row says which version it was checked against.