Be open to calls to discuss bugs or enhancement requests
Share your use cases with the Product Team
Steven Vanderberg | Product Manager, Marketo Engage Product Management | Adobe
I've been a user of said forbidden methods for a while (set up once years ago, and had just been chugging along). I recognize this was not recommended, but we needed it to get around some limitations (e.g. concurrency) with the REST API, so I'm glad this beta is an option and will surely be signing up.
Performing anonymous person association for thousands of leads in a short amount of time without this wasn't possible. We also defer all associations to wait for Salesforce to Marketo sync to occur, which is why they need to be done server side, otherwise we get duplicate leads.
@Steven_Vanderb3 in the meantime, I was wondering if the latest October release had finally shut the door on the forbidden server-side POST. On the night of October 16, we started getting a 404 response when trying to server-side POST and wanted to know if this was an intentional permanent change, and if this beta would be the best way to replace our previous integration.
@Steven_Vanderb3 we have been using the /save2 endpoint for years now and started to get a 404 error as of Saturday as well - the data is still making its way to Marketo as a form fill but I would like to know what is happening with this endpoint and a timeline if possible. We don't use Marketo forms because our forms require a lot of validation and logic that Marketo just can't provide out of the box, so we send to the endpoint. Also is there a distribution list where I can get updates like these? I don't get these at all or know where to go to signup for these kinds of notices.
Nothing was changed intentionally; there has been a reported change in behavior with the release that is being investigated by our Support team. This method of data entry isn't supported and will be blocked in the future but there will be an official deprecation announcement about that (take this as an unofficial heads up).
Thanks @Steven_Vanderb3. How will this be communicated? Anything I need to subscribe to?
I submitted a request to be part of the beta, but don't know what to expect in terms of feedback or acceptance into the closed beta. I also couldn't sign the agreement.
I'm working with our communication team on that question, but generally deprecations are announced on the Marketing Nation, Release Notes, and sometimes by email.
I've got multiple reports of the beta agreement not working and I'm having the team look into it.
In case anybody else is hitting this, I tried to sign up for the beta twice in Chrome and again in Safari, but I got an error when trying to sign the contract. The contract form just seems to be broken, but the signup itself is OK. I emailed Steven about it.
I know the beta is over, and the API has been released this past January (2021)
however, that API has a seemingly unsolvable problem: it does not works with duplicate emails. Because an email needs to be passed in, and it fails if there is more than one lead with that email, there is no way to update a duplicate with this API. Even if you were to make an additional call to fetch all matching leads, and determine which to update, there is no way to pass in another field or the Marketo ID to this SubmitFormUsingPOST to pick the lead to update.
Is there any plans to fix/address this?