API Issues with Partitions

API Issues with Partitions

Hi All-

We are onboarding a tool to help us capture form abandoners and the API integration is placing the test leads in the wrong partition and not our default 'new lead' partition. 


Every other API integration we have has worked no problem. Anyone have any experience with partition issues like this?

4 REPLIES 4
Level 10 - Community Moderator

Re: API Issues with Partitions

If it's the non-default partition then it needs to be specified in the API call. Without knowing which endpoint they're calling, impossible to give further guidance.

Re: API Issues with Partitions

Hi Sanford-

 

The leads aren't pushing into the default partition - and nothing is specified. We have tried using the field we use that designates partition and it didn't help. We have a handful of API integrations and have never faced this. Thanks for any insights!

Level 10 - Community Moderator

Re: API Issues with Partitions

It's not a (lead) field that determines the initial partition, but rather the explicit property partitionName in the payload of the API call.

 

Or you have some later logic that's picking up these leads and moving them, but if you don't have any other trigger campaigns interfering, then it's a matter of the partition being explicitly specified.

Level 1

Re: API Issues with Partitions

Recently started using the bulk API and had a similar issue.  For a bulk lead import that's not for the default partition, you also need to specify a static list ID to hold the results of the import (even if the file is updates only). 

An URL with query string would be:

/bulk/v1/leads.json?format=csv&lookupField=email&partitionName=MyPartition&listId=101