[randomdata]

API gets thrown around pretty loosely, but what Hubspot has isn't really an application programming interface. It is a state transfer service, as echoed in the documentation.

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.

[prng2021]

I've never used their API but the first google result for Hubspot API is their API reference documentation which starts with:

"HubSpot’s developer platform is a core part of our mission to empower organizations to grow better. Our APIs are designed to enable teams of any shape or size to build robust integrations that help them customize and get the most value out of HubSpot.

All HubSpot APIs are built using REST conventions and designed to have a predictable URL structure. They use many standard HTTP features, including methods (POST, GET, PUT, DELETE) and error response codes. All HubSpot API calls are made under https://api.hubapi.com and all responses return standard JSON."

If it's not actually an API in the traditional sense then that's absolutely awful documentation.

[thexumaker]

I disagree with this especially when they launched their "new" platform in 2020: https://developers.hubspot.com/docs/api/overview

> HubSpot’s developer platform is a core part of our mission to empower organizations to grow better. Our APIs are designed to enable teams of any shape or size to build robust integrations that help them customize and get the most value out of HubSpot. All HubSpot APIs are built using REST conventions and designed to have a predictable URL structure. They use many standard HTTP features, including methods (POST, GET, PUT, DELETE) and error response codes. All HubSpot API calls are made under https://api.hubapi.com and all responses return standard JSON.

I'm getting a bit more estate transfer implications in their old docs but barely

> The API is built to allow you to create a functional application or integration quickly and easily. We know from experience - these are the APIs that power the HubSpot application. The ecosystem of developers creating integrations on top of the APIs is strong and diverse, ranging from webinar providers to CRMs to social media.

Not really sure where they mention it as a state transfer service. Not to mention even if it was, their lack of support for over 50% of their workflow/sequence/queue automations products make state transfer impossible anyways even for internal teams.

[randomdata]

> I disagree

Glad to hear it. That means you don't have a problem (at least for some of the points raised).

[thexumaker]

Not sure how me pointing out none of their docs mention state transfer anywhere invalidates my issues with their API.

L take buddy

[randomdata]

It's right there in what you copied, or you could also look at the design. That will always tell you more than the words around it.

But, regardless, I am happy that you were able to solve your problem.

[thexumaker]

Man you’d fit right in at hubspot. Starts talking gibberish when a customer points out flaws.

[randomdata]

But seriously, I was hoping I could come work with you. I'm impressed by your developer prowess. I give you a short, somewhat vague explanation of how to deal with some of the issues you faced and within minutes you have it addressed and returned to joke around with me.

Most developers I know would spin their wheels for weeks with such little information, and once they finally get the job done they wouldn't have time to joke around because they'd be so far behind in everything else they need to get done.