APIs & Integrations

andrey_germanov
Member

Differencies in Contacts and Deals APIs

Just interesting, why the same options for very similar APIs have different names. For example, API call to get all Deals (/deals/v1/deal/paged) accepts "limit", "offset" and "properties" parameters, but similar API call to get all Contacts (/contacts/v1/lists/all/contacts/all) requires to use "count", "vidOffset" and "property" parameters for the same things.  Why is it ?  It makes API more confusing and requires from developer to create and maintain different functions for the same operation. Is it possible to change it to make API for different entities more uniform ?

0 Upvotes
1 Reply 1
jackcoldrick
HubSpot Employee
HubSpot Employee

Differencies in Contacts and Deals APIs

hi @andrey_germanov,

 

Thank you for the post and for providing this feedback. HubSpot API consistency and completeness has been a major point in feedback from our developer community for some time now. I agree this is confusing and to solve for this issue we've recently released a set of streamlined  CRM APIs to make this easier. If you'd like you can review them via the link below:

 

 

Right now they are in a stage that we call "Developer preview". During this time we are continuing to modify and tweak these endpoints based on feedback we collect from our developer community. You'll also notice the documentation is considerably different to our current documentation. This is the new format we're working towards.

 

Regards,

Jack

 

 

Jack Coldrick
Solutions Engineer @ HubSpot
Add me on LinkedIn