Rest API vs Mobile SDK | Community
Skip to main content
K
KARENBL
Level 5
January 20, 2016
Question

Rest API vs Mobile SDK

  • January 20, 2016
  • 3 replies
  • 1734 views

We are working with a 3rd party developer on an app in which our sales people can use to create/update leads within our system. Unfortunately this vendor has never integrated with Marketo and is unfamiliar with it. I recommended we use REST API for this, but they are stating that it is too difficult and suggested, if possible, if we can use Mobile SDK.  Any suggestions would be greatly appreciated,

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

3 replies

Kenny_Elkington
Adobe Employee
Kenny_ElkingtonAdobe Employee
Adobe Employee
January 20, 2016

You can only use the mobile SDK if you have a subscription to Marketo Mobile Engagement.  It is also extremely unlikely the any of the mobile SDKs would be useful since they rely on either the IOS or Android runtimes which are not available on typical servers.  Your vendor should use the REST API.

A
Anonymous
January 20, 2016

If this is an app run on IOS or Android then they should definitely use the Mobile SDK.  As Kenny mentioned, you will need a special license for it.

A
Anonymous
February 10, 2016

You can take a look at the official & community supported libraries here: GitHub - Marketo/Community-Supported-Client-Libraries: Community Supported Client Libraries

There are a number of libraries available in Java/C#/Python/Ruby/JavaScript/PHP which can speed up the integration.

SanfordWhiteman
SanfordWhiteman
Level 10
February 10, 2016

I'd be wary of any library that hasn't been updated in the past month (that's almost all of the libraries at the link). There are expensive commercial libraries that also aren't caught up with the latest Marketo API releases and/or don't implement functionality correctly.

I'd recommend starting with a REST/OAuth library, sure, but not a "Marketo-aware" library. The REST API is not exactly difficult to use (that's the advantage of REST). But the devil is in the details of the interface, and broken abstractions create confusion and/or a reduction in available functionality.

Terms & ConditionsAccessibility statement

Loading footer...