Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Any update on this? We have a need for this exact functionality.
I believe that the specific post endpoint "/rest/v1/lists/{listId}/leads.json" is being called out independent of the other API endpoints because it can actually really mess up your leads if you're not careful
Blocking field updates was released in November 2008. That is nearly nine years ago. Please enhance it to be role-based.
I agree with Sanford that you don't want to DoS yourself however if you have another use case that could benefit from a GetProgramsByLeadID endpoint I did add the idea to the Ideas forum here: and you could upvote it if you see fit.
We would like to query an API that would bring back all the programs a lead is a member of. Potential parameters could be date range, program types, tags a program may possess and more!The use case is: Whenever anyone in our instance is delivered an email we'd like to change a value of a custom fiel...
Hi Kenny, thanks for taking the time to ask for specifics. We were using:POST /rest/v1/leads/push.jsonIf someone got to our final checkout page (indicating they had successfully completed a transaction) we would push a program status to the lead. We hard coded name into our API call PushLeadToMarket...
It would be great if API parameters took an ID instead of a name for parameters, specifically where program name is a parameter. Program IDs don't change, the UI allows a user (likely in a completely different department) to change a program name and break something they may know nothing about.This ...