AnsweredAssumed Answered

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

Question asked by Dan Stevens.

on Feb 10, 2017
Latest reply on Feb 13, 2017 by Sanford Whiteman

Like • Show 1 Like1
Comment • 5

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?

Sanford Whiteman Feb 10, 2017 9:58 AM

Correct Answer

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.

See the reply in context

1 person had this question

Outcomes

Sanford Whiteman Feb 10, 2017 9:58 AM

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 person found this helpful

Actions

Dan Stevens.

@ Sanford Whiteman on Feb 10, 2017 10:34 AM

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

Actions

Sanford Whiteman @ Dan Stevens. on Feb 10, 2017 12:50 PM

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

Actions

Dan Stevens.

@ Sanford Whiteman on Feb 13, 2017 4:37 PM

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.

Actions

Sanford Whiteman @ Dan Stevens. on Feb 13, 2017 5:53 PM

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.

Actions

5 Replies

Sanford Whiteman Feb 10, 2017 9:58 AM
Unmark Correct
Correct Answer
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 person found this helpful
Like • Show 1 Like1
Actions
- Dan Stevens. @ Sanford Whiteman on Feb 10, 2017 10:34 AM
  Mark Correct
  Correct Answer
  Thanks Sandy. So if we have a basic Forms 2.0 form in our program, the endpoint URL should still contain save2?
  Like • Show 0 Likes0
  Actions
  - Sanford Whiteman @ Dan Stevens. on Feb 10, 2017 12:50 PM
    Mark Correct
    Correct Answer
    '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.
    Like • Show 0 Likes0
    Actions
    - Dan Stevens. @ Sanford Whiteman on Feb 13, 2017 4:37 PM
      Mark Correct
      Correct Answer
      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.
      Like • Show 0 Likes0
      Actions
      - Sanford Whiteman @ Dan Stevens. on Feb 13, 2017 5:53 PM
        Mark Correct
        Correct Answer
        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.
        Like • Show 0 Likes0
        Actions

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

Outcomes

Related Content

Recommended Content