REST API Won't Update Leads in Partitions

[Anonymous]

Hi,

I've seen a few discussions on this already in the community, but no answer has been provided by either Marketo or community member. I have a ticket open, waiting for a response...

We have partitions within our instance and are using our REST API to update leads upon form fills on our .com site. Our dev team has built this out previously (before partitions were added to our instance) and everything worked fine with creating new and or updating existing leads in the system.

Ever sense moving to partitions and workspaces, only new leads will be created in the system. We continue to experience a "partition update not allowed" error. Our api user has full permissions throughout the workspaces and permissions to all partitions.

Can anyone advise on how to update an existing lead through REST with partitions?

Thank you,

Tim

[Anonymous]

Are you specifying the partition when you upsert the leads? It's required to do so when you have partitions enabled in your instance, as noted here: Create/Update Leads » Marketo Developers

[Kenny_Elkington · Accepted solution]

This recent blog post should also be helpful: http://developers.marketo.com/blog/how-to-specify-lead-partitions-using-the-rest-api/

[Anonymous]

Thanks Kenny this is helpful. Quick question if you don't mind.

If a lead already exists in a partition, do we first have to make the call to figure out the partition it's in and then two call again to update the lead in the correct partition?

[Kenny_Elkington]

It's dependent on whether it's possible to infer this information externally.  In many cases the source from which you are synching will go only to a specific partition, or the known data about the lead will tell you which partition it is(or should be) a member of.  This is going to be dependent on your organization's business logic for partitions.  There may also be cases where data is insufficient to infer the partition.  It is generally a good idea to cache or store some of this information on the client-side so that API-lookups can be avoided, such as id, email and partition name.  It will lower your sync latency and help avoid round trips which will help keep you from using an unreasonable amount of API calls.

[Anonymous]

Nice, thank you Kenny. Very helpful again. Passing along to my dev.

[Anonymous]

Hi,

What if you have leads coming from various partitions? Can you identify 1. the leads existing partition and 2. update that lead in that partition?