API Issues with Partitions | Community
Skip to main content
Lauren_Temmler1
Lauren_Temmler1
Level 2
February 29, 2020
Question

API Issues with Partitions

  • February 29, 2020
  • 1 reply
  • 2717 views

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?

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

1 reply

SanfordWhiteman
SanfordWhiteman
Level 10
February 29, 2020

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.

    Lauren_Temmler1
    Lauren_Temmler1Author
    Level 2
    March 2, 2020

    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!

    SanfordWhiteman
    SanfordWhiteman
    Level 10
    March 2, 2020

    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.

    Terms & ConditionsAccessibility statement

    Loading footer...