Some of my complaints:
1. Hubspot released Sequences 10 years ago, and somehow they still don't have API suppport.
2. Meanwhile if I need to fetch associations between objects I have to use their V4 associations API but if I want to fetch contact lists I need to use their V1 API, and to fetch contacts themselves I sometimes have to use a V1 API and sometimes a V3 API. Who is versioning all of this
3. It's 2024 and somehow none of their APIs support sorting, ordering or filtering and to do so you need to use their /search endpoint. The problem is there's a 4 requests per second rate limit on the endpoint. That leads to my next complaint
4. A 4 rps limit is fine, if HubSpot allowed you to have an individual user go through oauth, but for some reason they suggest and push you to authenticate only 1 super admin, which means if you have 10+ users the search endpoint is pretty much useless and needs to be throttled significantly
There's so many other issues with fields that should be deprecated but aren't, fields getting deprecated and the only answers being some community message 5 years ago, lack of API support for workflows and other new features, and there's even issues where I noticed we'd get small bursts of 401's for no reason and Hubspot's response was that when they rotate the credentials used to verify tokens it can cause temporary downtime daily.
was done by people who did not receive the appropriated training in design patterns and has to glue something that worked in order to be proved by someone else
outside of a few orgs who chase excellency in every regard this is the reality for most companies, organizations and people. it makes sense given the circumstances they found themselves in.
it's actually quite impressive that anything works when you REALLY think about it
#
While am I sure their service is not free of flaws (the versioning as described comes off especially strange), the biggest issue here may be taking "API" too literally. What you are looking for is, indeed, an API, but that is not what they have on offer. Presumably their expectation is that you will build your API on top of the transferred state.
1. The might have had well supported API until the point at which they realized they wanted to have more people to use the webapp, rather than having the data sent through an API. More time spent on the Hubspot webapp means, more chances the customer notices the other services Hubspot provides and pays for them.
2. The versioning APIs that you see are most likely due to an enterprise deal Hubspot made with a large company who asked for variations in the API, and Hubspot introduced a v2/v3/v4 instead of modifying v1 (to not cause disruptions for their customers using v1).
Support for If-Match seems like a low bar and yet few clear it.
When asked about data quality issues (“data in a weird state” or “shouldn’t be possible”) and the API has zero protection for lost updates… I sigh. Nothing to do.