difference between v1 apis and v3 apis

cb-madhukiran1
Member

Hi Team,

I noticed that some of the API capabilities that are present in v1 are not present in v3. How do we go about this? Our app integration is trying to apply for the app certification where I came across this point. 

  • Your app must be built using the latest stable versions of our APIs.

For example:

Get a contact by email which is in v1 there is no corresponding API in v3:

 

https://legacydocs.hubspot.com/docs/methods/contacts/get_contact_by_email

So what is the corresponding v3 API that I can find? Let me know if I m missing something?

 

 

0 Upvotes
3 Replies 3
WendyGoh
HubSpot Employee

Hey @cb-madhukiran1,

 

The v1 APIs are still stable to use and here's a list of deprecated APIs that your team should keep a look out for: HubSpot APIs | Deprecated APIs.

 

Having said that, if you're looking to get contact by their email, you can use the: CRM API | Search

 

Here's an example of the POST body

curl https://api.hubapi.com/crm/v3/objects/contacts/search?hapikey=YOUR_HUBSPOT_API_KEY \
  --request POST \
  --header "Content-Type: application/json" \
  --data '{
    "filterGroups":[
      {
        "filters":[
          {
            "propertyName": "email",
            "operator": "EQ",
            "value": "hstest@hubspot.com"
          }
        ]
      }
    ]
  }'
0 Upvotes
cb-madhukiran1
Member

Hi @WendyGoh, Thanks for your reply. I would like to know a few more details
1. Is it a mandatory requirement for app certification to implement batching for APIs, or is it kind of good to have? This has been listed on the certification page. 

https://developers.hubspot.com/docs/api/certification-requirements

2. the rate limit mentioned on the same page is it per access token (100/ 10 secs) or overall app across access tokens can receive 100 per 10 seconds?

 

0 Upvotes
WendyGoh
HubSpot Employee

Hey @cb-madhukiran1,

 

To answer your questions:

 

1. It is not mandatory to implement the batch APIs however, it is highly recommended to avoid hitting the TEN_SECONDLY_ROLLING limit. 

 

2. As Connor mentioned here

The secondly limit is actually 10/second per app install. So the number of access tokens generated wouldn't actually matter.

Additionally, do note that the Search API endpoints are rate limited to four requests per second per authentication token

0 Upvotes