Has the HTTP POST endpoint URL changed from "/save2" to just "/save"? | Community
Skip to main content
Dan_Stevens_
Dan_Stevens_
New Participant
February 10, 2017
Solved

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

  • February 10, 2017
  • 1 reply
  • 6704 views

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? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

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.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
February 10, 2017

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_
Dan_Stevens_Author
New Participant
February 10, 2017

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

SanfordWhiteman
SanfordWhiteman
New Participant
February 10, 2017

'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.

Terms & ConditionsAccessibility statement

Loading footer...