Consider adding API route to get all Leads associated with a Person (/v1/persons/{id}/leads)

API
1

Would an API route that lists all of the Leads associated with a Person be considered for addition to the API?

There is currently an API route that lists all of the Deals associated with a Person (/v1/persons/{id}/deals), but there’s not one for /v1/persons/{id}/leads.

This would be great to have! My use case would be checking for already open/non-archived Leads for a Person before creating a new one.

Currently, I’m going to have to try using the /v1/leads/search API route, but a term parameter is required while I don’t want to use one (I just want any Lead associated with the person_id I pass).

1 Like
2

Hi @jketcham
Thanks for the excellent feedback :slight_smile: Having the use-case associated with the requests definitely helps a lot! We are currently studying the areas of improvement for our Public API and leads is one of the areas that we would like to prioritize. Right on time :wink: !

1 Like
3

Hi, this would still be very useful to me. Right now I have to search leads by title and then filter by person_id. Can’t even search leads on email via the node api, because fields must be one of [custom_fields, notes, title].

It would be great to be able to do personApi.getPersonLeads(person_id) instead of leadsApi.serachLeads(customer_title_string_that_we_hope_matches, {person_id: person_id})