What This Update Actually Is
HubSpot added two new API capabilities to the external meetings API under /v3/meetings/meeting-links.
First, a new PATCH endpoint lets developers attach or remove a payment link from a scheduling page slug. Second, the existing GET endpoint now returns the paymentLinkId field in list responses, so you can see at a glance which scheduling pages already have payment links tied to them.
Before this update, associating a payment link with a meeting scheduling page was a manual step inside the HubSpot UI. There was no programmatic path. If your team managed dozens of scheduling pages or needed to build that logic into a custom app or integration, you were stuck clicking.
Why HubSpot Shipped This
HubSpot has been steadily building out its payments and commerce layer. The goal is to let revenue-generating actions happen closer to the point of conversation. Paid meetings are a real use case: consultants, coaches, fractional leaders, and high-touch sales teams all charge for discovery calls or advisory sessions.
The external frustration was real. Humans building multi-portal or multi-product systems had no way to set up or adjust payment link associations without logging into the UI manually. That breaks any serious automation or provisioning workflow.
The internal frustration was just as sharp. Ops teams who manage payment link configurations across many scheduling pages had no audit trail or bulk management path. The read side of this update alone, knowing which pages have payment links attached, is genuinely useful for data hygiene and reporting.
How to Use It Step by Step
Here's the practical path for developers implementing this update:
- Confirm your portal has an active HubSpot Payments account. Without it, the PATCH endpoint will reject any request to attach a payment link.
- Request the correct scopes. PATCH requires PAYMENT_LINKS_WRITE plus either meeting ownership or MEETING_CREATION_ACCESS. GET requires PAYMENT_LINKS_READ; without it, the paymentLinkId field is simply omitted from the response.
- Grab the scheduling page slug. The slug is the path parameter for the PATCH endpoint. It's the unique identifier for the scheduling page, not the full URL.
- To attach or change a payment link, call PATCH /v3/meetings/meeting-links/{meetingLinkSlug} with a body of {"paymentLinkId": <crmObjectId>}. Replace <crmObjectId> with the numeric ID of the payment link object in your CRM.
- To remove a payment link, send the same PATCH call with {"paymentLinkId": null}. That clears the association without deleting either the scheduling page or the payment link.
- To audit existing associations, call GET /v3/meetings/meeting-links. If your token has PAYMENT_LINKS_READ scope, each scheduling page record in the response will include its paymentLinkId where one exists.
- Test in a sandbox first. Payment link associations affect what a prospect sees at checkout. A misconfigured link on a live scheduling page means a prospect hits a broken or wrong payment flow.
What It Touches in Your HubSpot Strategy
This update sits at the intersection of three HubSpot areas: meetings/scheduling, payments/commerce, and the developer API layer. Let's look at where it ripples.
On the commerce side, this connects directly to HubSpot's growing payments infrastructure. If your portal is already using payment links at checkout, this API update opens the door to managing those links programmatically across your scheduling pages at scale. That's especially relevant if you've been watching HubSpot's expanding checkout options like Affirm and Klarna support, since each new payment method adds complexity that's easier to manage via API than through manual UI updates.
Key Takeaway
The read side of this update is underrated. Just knowing which scheduling pages have payment links attached gives ops teams a real audit capability they didn't have before. Pair it with a nightly GET call and you have a living inventory of your paid meeting setup.
On the RevOps side, this update pairs well with other API-first moves HubSpot has been making. If you're building a broader developer layer on top of your portal, think about how this connects to other programmatic sales tools. The Sales Templates Public API update is another good example of HubSpot giving developers programmatic control over what used to require manual UI work. These updates compound. The more of your portal you can manage via API, the more resilient your processes become.
On the meetings side, this update complements the calendar and scheduling toolset. If your team is already thinking through how meeting bookings work at scale, it's worth pairing this with what HubSpot shipped around calendar detail visibility when booking on behalf of others. Both updates push toward a more controlled, permission-aware scheduling system.
Key Takeaway
This isn't a clicks-in-the-UI update. If your team doesn't have a developer or an integration that calls the meetings API, this update doesn't change your day. But if you do, it removes a real manual bottleneck and adds a clean audit path for payment link associations.
Who Should Care Most
This is a developer-facing update. Not every HubSpot practitioner needs to act on it. Here's who does:
- Developers building custom HubSpot apps who need to configure paid scheduling pages as part of onboarding flows, provisioning scripts, or multi-portal management tools.
- RevOps leaders at companies with a large number of scheduling pages who need to audit which pages are gated behind payment and which aren't, without manually clicking through each one.
- Agencies and partners managing multi-client portals who set up paid meeting configurations as part of client onboarding and want a repeatable, API-driven process instead of manual setup each time.
- Businesses on Sales Hub or Service Hub Pro/Enterprise that already use HubSpot Payments and charge for time-based services like consulting, coaching, or advisory calls.
If you're a solo marketer on Starter, this isn't for you yet. The permissions and tier requirements are specific, and HubSpot Payments must already be active for the PATCH write capability to work at all.
George's Take
What I find compelling about this update isn't the endpoint itself. It's the pattern it represents. HubSpot is making a deliberate move to expose its commerce layer to the API, which means the humans who build on top of HubSpot now have the same control over payment configurations that they've had over contacts and deals for years. That matters. Paid scheduling isn't a niche use case anymore. It's how a growing number of service businesses operate. When I look at portals where payment friction shows up, it's almost always because someone had to configure things manually and something slipped. An API-first path fixes that class of problem entirely.
“HubSpot opening its payments layer to the API isn't a minor tweak. It's the beginning of a fully programmable revenue layer, and the teams who build on it now will have a serious head start.”
If you're not sure how this fits your portal's current setup, or you want to think through where API-driven automation could reduce manual work across your meetings, payments, and sales process, let's talk. Book a strategy call with the Sidekick team and we'll help you figure out exactly where this update (and others like it) fit into your HubSpot strategy.
Frequently Asked Questions
What does the HubSpot meeting links payment link API update do?
It adds two API capabilities: a PATCH endpoint to attach or remove a payment link from a scheduling page, and an updated GET endpoint that now returns the paymentLinkId for each scheduling page. This lets developers manage paid meeting configurations programmatically instead of doing it manually in the HubSpot UI.
What scopes are required to use the meeting links payment link API?
The PATCH endpoint requires PAYMENT_LINKS_WRITE scope, plus either ownership of the meeting link or MEETING_CREATION_ACCESS scope. The GET endpoint requires PAYMENT_LINKS_READ scope. Without that scope, the paymentLinkId field is simply omitted from the response rather than returning an error.
Do you need an active HubSpot Payments account to use this API update?
Yes. You need an active payments account on your portal to attach a payment link via the PATCH endpoint. The GET endpoint will still return scheduling page data without an active payments account, but the paymentLinkId will be absent if no payment links are associated.
How do you remove a payment link from a HubSpot scheduling page via API?
Send a PATCH request to /v3/meetings/meeting-links/{meetingLinkSlug} with a body of {"paymentLinkId": null}. This clears the payment link association from the scheduling page without deleting either the page or the payment link object itself.
Which HubSpot tiers get access to the meeting links payment link API update?
This update is available on Sales Hub Professional, Sales Hub Enterprise, Service Hub Professional, and Service Hub Enterprise. It's not available on Free or Starter tiers.
Can this API update be used to audit which scheduling pages have payment links?
Yes. The GET /v3/meetings/meeting-links endpoint now returns paymentLinkId in its list response when the caller has PAYMENT_LINKS_READ scope. This makes it straightforward to build an audit script that inventories all scheduling pages and flags which ones have payment links attached.
