Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
2 added 348 characters in body
source | link

Is this even possible yet? I have gotten my script up to the point of creating HTML emails in Content Builder and as I understand it, I have three options from there:

  1. Send it to a Journey step. My client does not have JB provisioned, so I cannot do that.

  2. Send a single transactional email to a single user. This isn't our use case. We are trying to have automated mass sends.

  3. Rebuild the email in SOAP and send it via classic content. The client already has this in place and we really wanted to keep it in one email service (classic content vs content builder). The whole project was to convert the old classic content/SOAP API send that was in place and swap to content builder/REST.

Is that it? Is the functionality to send to a data extension just non-existent through REST and content builder? I saw a few other threads that mentioned compiling it and sending the compiled version, but that is still creating it in classic content right?

EDIT: It looks like PeterB was trying to do this same thing two years ago. Still not possible?

Sending Content Builder templates/emails via the SOAP API

Is this even possible yet? I have gotten my script up to the point of creating HTML emails in Content Builder and as I understand it, I have three options from there:

  1. Send it to a Journey step. My client does not have JB provisioned, so I cannot do that.

  2. Rebuild the email in SOAP and send it via classic content. The client already has this in place and we really wanted to keep it in one email service (classic content vs content builder). The whole project was to convert the old classic content/SOAP API send that was in place and swap to content builder/REST.

Is that it? Is the functionality to send to a data extension just non-existent through REST and content builder? I saw a few other threads that mentioned compiling it and sending the compiled version, but that is still creating it in classic content right?

Is this even possible yet? I have gotten my script up to the point of creating HTML emails in Content Builder and as I understand it, I have three options from there:

  1. Send it to a Journey step. My client does not have JB provisioned, so I cannot do that.

  2. Send a single transactional email to a single user. This isn't our use case. We are trying to have automated mass sends.

  3. Rebuild the email in SOAP and send it via classic content. The client already has this in place and we really wanted to keep it in one email service (classic content vs content builder). The whole project was to convert the old classic content/SOAP API send that was in place and swap to content builder/REST.

Is that it? Is the functionality to send to a data extension just non-existent through REST and content builder? I saw a few other threads that mentioned compiling it and sending the compiled version, but that is still creating it in classic content right?

EDIT: It looks like PeterB was trying to do this same thing two years ago. Still not possible?

Sending Content Builder templates/emails via the SOAP API

1
source | link

Fuel-Rest API using Content Builder send to Data Extension

Is this even possible yet? I have gotten my script up to the point of creating HTML emails in Content Builder and as I understand it, I have three options from there:

  1. Send it to a Journey step. My client does not have JB provisioned, so I cannot do that.

  2. Rebuild the email in SOAP and send it via classic content. The client already has this in place and we really wanted to keep it in one email service (classic content vs content builder). The whole project was to convert the old classic content/SOAP API send that was in place and swap to content builder/REST.

Is that it? Is the functionality to send to a data extension just non-existent through REST and content builder? I saw a few other threads that mentioned compiling it and sending the compiled version, but that is still creating it in classic content right?