Has the HTTP POST endpoint URL changed from "/save2" to just "/save"?

[Dan_Stevens_]

We have a legacy application that still uses the old HTTP POST method to get data from a third-party form into Marketo.  I know, we should be using the Forms 2.0 API - and are for all future development.  But just recently, data is no longer entering Marketo.  We always used the endpoint URL that contained "/index.php/leadCapture/save2".  But when I ran a quick test and placed the form on a Marketo LP, and then looked at the source code, it now contains "/index.php/leadCapture/save" (without the "2").  Was this changed recently? 

[SanfordWhiteman · Accepted solution]

The plain HTML form uses /save, JS-enhanced and embedded forms use /save2. This has been true for a long time.

The semantics are slightly different and /save is actually better IMO if you are forced to do a third-party POST.

[Dan_Stevens_]

Thanks Sandy.  So if we have a basic Forms 2.0 form in our program, the endpoint URL should still contain save2?

[SanfordWhiteman]

'pends on what you want to happen upon POST. /save is useful for integrating with foreign platforms like Wix/Unbounce/etc. because it returns a pure HTTP redirect on success, as opposed to a JSON result.

[Dan_Stevens_]

Sandy, just out of curiosity, does this approach fail if our API limits have been reached?  Apparently, every day that these tests failed were days where we exceeded our 10,000 API calls.

[SanfordWhiteman]

Not direclty, but if your daily traffic was enough to overwhelm the (REST) API limits it stands to reason that other limits (30 form posts/60 seconds) could be exceeded during the same period.