Send email from a Heymarket inbox or reply in an existing thread. HTML is supported in the body. Use convo_id to keep replies in the same email conversation.
curl --request POST \
--url https://api.heymarket.com/v1/email/send \
--header 'Content-Type: application/json' \
--data '
{
"creator_id": 123,
"inbox": 123,
"text": "<string>",
"raw_text": "<string>",
"local_id": "<string>",
"conv_title": "<string>",
"targets": [
"<string>"
],
"convo_id": 123
}
'{
"id": 123,
"convo_id": 123,
"queued": true,
"date": "<string>",
"compliance_results": {}
}convo_id. HTML is supported in the message body.
local_id will not create a second message.convo_id).to: or cc:. For example:["to:alice@example.com,bob@example.com", "cc:carol@example.com"]
targets when starting a new conversation. To reply in an existing thread, use convo_id instead.convo_id field in the initial send response. Providing this keeps all messages in the same email thread.true if the message has been queued for delivery.curl --request POST \
--url https://api.heymarket.com/v1/email/send \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{
"creator_id": 55,
"inbox": 202,
"convo_id": 10045,
"text": "<p>Thanks for reaching out! We have processed your refund.</p>",
"raw_text": "Thanks for reaching out! We have processed your refund."
}'
text field. Use raw_text to provide a plain-text fallback for email clients that do not render HTML.convo_id. You can find this value in the response from the first send request that created the conversation.Was this page helpful?
curl --request POST \
--url https://api.heymarket.com/v1/email/send \
--header 'Content-Type: application/json' \
--data '
{
"creator_id": 123,
"inbox": 123,
"text": "<string>",
"raw_text": "<string>",
"local_id": "<string>",
"conv_title": "<string>",
"targets": [
"<string>"
],
"convo_id": 123
}
'{
"id": 123,
"convo_id": 123,
"queued": true,
"date": "<string>",
"compliance_results": {}
}