* If you publish your email, you can copy the email ID from the email details page.
Use these properties when you want to set a contact property while you’re sending the email. For example, when sending a receipt you may want to set a `last_paid_date` property, as the sending of the receipt will have information about the last payment.
```json theme={null}
{
"emailId": 4126643121,
"message": {
"to": "jdoe@hubspot.com",
"sendId": "6"
},
"contactProperties": {
"last_paid_date": "2022-03-01",
"firstname": "jane"
}
}
```
#### customProperties
The `customProperties` field is a JSON object of key-value properties. These properties are generally related to the email itself, not the contact receiving the email. They will not appear in the [web page version of the email](https://knowledge.hubspot.com/marketing-email/create-a-web-version-of-your-marketing-email), or in the view of the email from the contact's timeline. These properties are also not stored in HubSpot and will only be included in the sent email.
Each key in the `customProperties` field can be referenced in the template using a [HubL expression](/cms/reference/hubl/overview) for fields contained within the `custom` variable (e.g., `{{ custom.NAME_OF_PROPERTY }}` ).
For example, if your email template references two properties, `purchaseUrl` and `productName`, you could provide the associated values for these properties with the following request body:
```json theme={null}
{
"emailId": 4126643121,
"message": {
"to": "jdoe@hubspot.com",
"sendId": "6"
},
"customProperties": {
"purchaseUrl": "https://example.com/link-to-product",
"productName": "vanilla"
}
}
```
You can then reference these properties in your email template:
```hubl theme={null}
Congrats on purchasing some of the best ice cream around.
{{custom.productName}} ``` The `customProperties` field only supports arrays when used with [programmable email content](/cms/start-building/features/data-driven-content/emails-with-programmable-content). In your email template, you can reference the items defined in your `customProperties` field by using a [HubL expression](/cms/reference/hubl/overview) (e.g., using a [for loop](/cms/reference/hubl/loops) to render each item in a list). For example, if the `customProperties` you included in your request body was structured like the following JSON snippet below: ```json theme={null} { "emailId": 4126643122, "message": { "to": "jdoe@hubspot.com", "sendId": "7" }, "customProperties": { "exampleArray": [ { "firstKey": "someValue", "secondKey": "anotherValue" }, { "firstKey": "value1", "secondKey": "value2" } ] } } ``` You could then reference the values for each item in `exampleArray` with the following HubL code: ```hubl theme={null}Thanks for your recent purchase! Here are the details of the items you'll be receiving:
-
{% for item in custom.exampleArray %}
- First key: {{ item.firstKey }}, Second key: {{item.secondKey}} {% endfor %}
### Response
The response contains the following fields:
| Field | Type | Description |
| ------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `sendResult` | String | An enumeration that represents the email's send status. The possible values are [listed below](#sendresult-values). |
| `requestedAt` | String | An ISO 8601 formatted timestamp from when the send was requested. |
| `startedAt` | String | An ISO 8601 formatted timestamp from when the send began processing. |
| `message` | String | A supplementary message describing the result. |
| `completedAt` | String | An ISO 8601 formatted timestamp when the send completed. |
| `statusId` | String | An identifier that can be used to [query the status of the send](#query-the-status-of-an-email-send). |
| `status` | String | The status of the send request. Possible values are: `PENDING`, `PROCESSING`, `CANCELED`, and `COMPLETE`. |
| `eventId` | Object | If sent in the original request, this object will be included in the response, which includes two fields: - `id`: the ID of the sent event.
- `created`: an ISO 8601 formatted timestamp of the sent event
- `id`: the ID of the sent event.
- `created`: an ISO 8601 formatted timestamp of the sent event