Hello @PCronin9
Why does a v4 CRM Objects API also exist, but is mentioned neither in the endpoint’s response, nor mentioned in the developer API docs?
The v4 CRM Objects API is a newer version of the API that is still under development. It is not yet fully supported, and that is why it is not mentioned in the endpoint’s response or the developer API docs.
What is the difference between the LATEST and STABLE “stages” included in the response from the v1/apis endpoint mentioned above?
The LATEST stage indicates that the API is the newest version and is recommended for use. The STABLE stage indicates that the API is a stable version that is fully supported.
The v4 CRM associations API is listed as STABLE because it is a newer version of the API that is more feature-rich than the v3 CRM associations API. However, the v3 CRM associations API is still fully supported and is listed as LATEST because it is the most widely used version of the API.
Why have I observed at least one change to the OpenAPI specs, while the API version remained at “v3”?
HubSpot occasionally makes changes to the OpenAPI specs without changing the API version. This is typically done to make minor changes or to fix bugs.
Are changes to the OpenAPI specs announced any where? How can I find out if I need to regenerate my client libraries?
HubSpot does not announce changes to the OpenAPI specs. However, you can check the endpoint’s response or the developer API docs periodically to see if there have been any changes.
Is it possible to access older versions of OpenAPI specs? Specifically, previous versions of the various v3 CRM OpenAPI specs, not v2, v1, etc.
No, it is not possible to access older versions of OpenAPI specs. HubSpot only publishes the latest version of the OpenAPI specs for each API.
Why is the “Basic List” endpoint that returns the existing associations between a particular object type/id and another object type not included in the OpenAPI spec for the v4 CRM associations?
The “Basic List” endpoint is a new endpoint that is still under development. It is not yet fully supported, and that is why it is not included in the OpenAPI spec.
Why was the bug in the v4 CRM Associations dev docs not fixed?
HubSpot is aware of the bug in the v4 CRM Associations dev docs and is working on fixing it.
Moderator note: Community Champions, like Himanshurauthan, are not HubSpot employees, but enthusiastic volunteers committed to helping and supporting everyone in the community.
Alongside users, certified partners, and HubSpot employees, Champions play a key role in moderating the community and fostering a positive environment for all.