HubSpot Commerce Hub API Is Now Live!

[dennisedson]

We are pleased to announce the general availability of the read-only endpoints for the HubSpot Commerce Hub API. This API provides programmatic access to core Commerce Hub data objects, including Invoices, Subscriptions, and Payments.

What's new?

Previously, there was no way to access Commerce Hub data programmatically. Now, we're introducing a read-only API that allows you to seamlessly query and retrieve data from key Commerce Hub objects:

• Invoices
• Subscriptions
• Payments

What can you do with it?

This new API opens a world of possibilities for customizing and extending your Commerce Hub experience. Here are just a few examples:

• Enhanced Customer Dashboards: Integrate Commerce Hub data into your existing dashboards and customer portals, allowing customers to view their open invoices directly within another application.
• Streamlined Workflows: Automate tasks by programmatically fetching data like a customer's payment history and syncing it with external systems.
• Custom Reporting: Build custom reports that combine Commerce Hub data with information from other sources, providing a more comprehensive view of your B2B commerce activities.

[CYM-Chris]

@dennisedson Is enhanced customer dashboards actually possible yet? It looks like we can access the null association end points yet and most client-facing executions I am aware of involve someone logging into a web-based area and then showing them records and info associated with their email address/ contact record.

When trying this for the Commerce Hub objects right now, my developer friend shared this screenshot showing the last line: Built-in object type 'COMMERCE_PAYMENT' is not yet supported.

[akhalsa]

Hi @CYM-Chris , 

Are you able to share the API endpoint being used to fetch the associations? Using the associations API endpoint GET /crm/v4/objects/{objectType}/{objectId}/associations/{toObjectType} I was able to fetch the associated commerce payment object ids. For example something along the lines of GET /crm/v4/objects/contact/100/associations/commerce_payment should fetch the associated commerce payment objects for the contact with object id 100.  

[CYM-Chris]

This makes sense but it doesn't solve the issue of getting the objects with HubL.

[akhalsa]

Thanks for the context of this being around HubL! I'll reach out to the team that owns the HubL functionality to see if we can add support there. 

[CYM-Chris]

Thank you!!

[akhalsa]

Hey @CYM-Chris ,

I have some good news that this should be working now and verified using the HubL association function in the screenshot. 

[CYM-Chris]

Yeah!!!! You guys are awesome. I will get with the developer to confirm on our end.

[CYM-Chris]

Hey @dennisedson & @akhalsa , I am adding this here instead of a new thread because it is the same problem as before except with the new native objects.

We are experiencing the same "Not supported by HubL" problem for these objects:

Orders

Carts

Appointments

Courses

Listings

Services

Is this something that can be fixed quickly like last time?

[CIPS]

This is very cool but do we have an estimated date for enabling update, create, and associate endpoints?

[jperro]

@CIPS hello! Joe here from the product team at HubSpot. While I don't have a concrete timeline I can share just yet, we are considering full read/write API access for later this year. As we firm up our plans, I'll circle back here with more information.

Can I ask - what use cases are you most looking forward to solving with full API access?

[CIPS]

Thanks for the update. I'd like to update HubSpot Invoices from Make or from other workflows. Right now, when you update an associated Invoice from workflow, it updates ALL associated invoices, which is probably always a bad option. I also had use cases to update a HubSpot invoice from a Make scenario, for example, to put the run ID that created the invoice. Overall the tool is extremely limited and we had to create a ton of workarounds which then generated more issues. Its not been the best experience integrating invoices with other systems.