SOLVED

CLARIFY: If Forms is a REST API, why does it use SOAP names?

Go to solution
Highlighted
Level 8

CLARIFY: If Forms is a REST API, why does it use SOAP names?

In using the form.vals function for external forms, I was under the impression that it would use the REST API field names since it's a REST API. To get the function to work correctly, the SOAP field names need to be used. This is doin' me a confuse...can someone clarify why a REST API would use SOAP naming?

Here's an example of working code:

form.vals({"Phone":"{{lead.Phone Number}}",

                 "FirstName":"{{lead.First Name}}",

                 "LastName":"{{lead.Last Name}}",

                 "Company":"{{company.Company Name}}",

                 "Email":"{{lead.Email Address}}",

                 "State":"{{lead.State}}",

                 "Title":"{{lead.Job Title}}",

                 "City":"{{lead.City}}",

                 "Address":"{{lead.Address}}",

                 "PostalCode":"{{lead.Postal Code}}"

                });

And here are the field names, as exported:

 

REST API NameSOAP API NameFriendly Label

firstNameFirstNameFirst Name

 

lastNameLastNameLast Name

 

companyCompanyCompany Name

 

emailEmailEmail Address

 

stateStateState

 

titleTitleJob Title

 

phonePhonePhone Number

(Etc)

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Level 10 - Community Moderator

Re: CLARIFY: If Forms is a REST API, why does it use SOAP names?

The client-side Forms API isn't a REST API.

View solution in original post

2 REPLIES 2
Highlighted
Level 10 - Community Moderator

Re: CLARIFY: If Forms is a REST API, why does it use SOAP names?

The client-side Forms API isn't a REST API.

View solution in original post

Highlighted
Marketo Employee

Re: CLARIFY: If Forms is a REST API, why does it use SOAP names?

Here is a cheat sheet for which field name to use:

Where to Use Which Field Name Version