Also after I was finally able to get the calls to work, I realized how terriblly inefficient my orignal code was. Looked at@SanfordWhitemanarticlehttps://blog.teknkl.com/and-yes-fl...
I started another discussion in hopes of resurrecting the conversation in case you want to follow there if answers arise.https://nation.marketo.com/t5/product-discussions/custom-ac...
I started a new discussion in case you want to follow for potential answers.
https://nation.marketo.com/t5/product-discussions/custom-activity-datetime-attributes/m-p/326440/highl...
I started a new threadhttps://nation.marketo.com/t5/product-discussions/custom-activity-datetime-attributes/m-p/326440/highlight/true#M184271if you would like to follow there in ca...
I have seen several old conversations about this topic with no resolutions so I am going to start a new one.
I am creating a custom event with the following request
{
"input": [{
...
So you never got an answer to this? Because I am seeing something similar.
My instance is set at EDT when I look in the admin and being that we are in June we are definitely in Ea...
well the entire urlhttps://975-FPO-828.mktorest.com which is our marketo instance and should meet all of the criteria listed and yet I still get the error posted