What This Update Actually Is
HubSpot published updated requirements for listing, certifying, and recertifying apps in the HubSpot Marketplace. These changes affect any app that isn't already listed. Apps currently live in the Marketplace are not affected by the listing rules.
Here's exactly what changed for new listings:
- Apps must run on a supported HubSpot developer platform version. Starting November 2, 2026, apps built on legacy versions or project versions 2023.1, 2023.2, or 2025.1 will be denied.
- App cards are now required. Legacy CRM cards are no longer permitted on new listings.
- OAuth v3 endpoints are mandatory. The older OAuth flows won't pass review.
- Demo videos or guided walkthroughs are now required on the listing page. Testing credentials are no longer accepted as a substitute.
Certification and recertification requirements have also been updated separately. HubSpot noted these will be refreshed periodically to maintain quality and security. Apps applying for certification that don't meet the latest requirements will be denied, but they won't be pulled from the Marketplace if they're already listed.
Why HubSpot Shipped This
The external problem is real: the Marketplace has accumulated apps built on older platform frameworks. As HubSpot's APIs, CRM objects, and UI components have evolved, some of those legacy apps have become compatibility risks. They can break, expose security gaps, or behave unpredictably inside modern portals.
The internal frustration is just as real. Humans who manage HubSpot portals for growing companies often install Marketplace apps without knowing which platform version they're built on. When something breaks, diagnosing the cause is painful. A poorly built app can create data problems that ripple through your CRM for months.
HubSpot's stated goal is a higher-quality, more secure Marketplace that keeps pace with the platform itself. Tighter listing standards at the gate mean fewer problem apps make it in. That's a win for every team that depends on third-party integrations to run their revenue operations.
How to Use It Step by Step
This update is primarily action-required for app developers, not end-users. But if you're evaluating, recommending, or managing integrations, here's how to navigate it correctly.
- Check your developer platform version. If you're building or maintaining an app, confirm it's on a currently supported version. Avoid 2023.1, 2023.2, and 2025.1 for any new listing attempts after November 2, 2026.
- Replace legacy CRM cards with app cards. HubSpot's newer app card framework is the required standard. If your app still uses legacy CRM cards, rebuild those components before submitting.
- Migrate to OAuth v3 endpoints. Audit your app's authentication flow. If you're on an older OAuth version, this is a hard requirement. Update your endpoints before submission.
- Record a demo video or guided walkthrough. This replaces the old testing-credentials requirement. Keep it clear, show real functionality, and make it easy for a HubSpot reviewer to understand what your app does.
- Review the full certification requirements before applying or reapplying. These are updated periodically, so don't rely on requirements you reviewed six months ago. Check HubSpot's changelog for the latest technical details.
- Submit a support form if you have technical questions. HubSpot has a dedicated support path for Marketplace technical issues. Don't guess. Use it.
What It Touches in Your HubSpot Strategy
For most HubSpot users, this update is invisible in day-to-day portal work. But for operations leaders and RevOps humans who manage integrations, it carries meaningful implications.
Integration evaluation gets more reliable. When you know new listings must pass modern standards, you can trust that a freshly approved Marketplace app is less likely to break against current HubSpot APIs. That changes how you evaluate third-party tools in your tech stack reviews.
CRM data integrity gets a quiet protection layer. Legacy CRM cards and old OAuth flows are common sources of sync errors, duplicate records, and missing data inside HubSpot. Blocking them from new listings reduces the attack surface for those problems. If you've ever chased a mysterious data gap back to a third-party app, you know exactly how much this matters.
Key Takeaway
Apps already listed in the Marketplace are not affected by the new listing requirements. Only new submissions and certification or recertification attempts must meet the updated standards.
Vendor due diligence changes, too. If you're evaluating a Marketplace app that was listed before these requirements took effect, ask the vendor directly: are you on a supported platform version? Do you use OAuth v3? Are you planning recertification? Those are now legitimate questions that have clear, verifiable answers.
If your RevOps stack includes the Salesforce integration, this update is worth reading alongside HubSpot's Salesforce sync engine rebuild. Both signal a platform-wide push toward modern, secure, stable connections between HubSpot and external systems.
Key Takeaway
The November 2, 2026 deadline for legacy app versions is a hard cutoff. If you're a developer or an agency building custom Marketplace apps, don't wait until October to audit your platform version.
This update fits a broader pattern of HubSpot cleaning up technical debt across the platform. Similar to how pipeline-level control over stage calculated properties helps teams avoid property bloat, tighter Marketplace standards help teams avoid integration bloat. Both move HubSpot portals toward cleaner, more intentional architecture.
Who Should Care Most
This update matters most to three groups. Know which one you are, and act accordingly.
- App developers and ISVs building on HubSpot. If you have an app in progress or plan to submit one, the November 2, 2026 deadline is non-negotiable. Audit your platform version, card framework, and OAuth flow now.
- HubSpot agency partners and solutions providers. If your agency builds or recommends Marketplace apps, this changes your vetting checklist. Humans at your client companies are relying on you to catch this stuff before it causes problems.
- RevOps and operations leaders managing multi-app portals. You're not submitting apps, but you are responsible for what's installed. Use this moment to review your active integrations and ask vendors about their certification status.
If you're a business owner on HubSpot Professional or Enterprise, this is mostly background news unless your team is actively building or evaluating integrations. In that case, loop in your ops lead.
George's Take
I've seen what happens inside portals when a poorly built integration gets installed without a second thought. It starts small: a missing property, a duplicate contact, a workflow that fires when it shouldn't. By the time someone traces it back to a legacy app using outdated CRM cards, the cleanup is brutal. HubSpot raising the bar here isn't red tape. It's platform hygiene. Humans who run serious operations on HubSpot deserve integrations that are built to current standards, and this update is how HubSpot enforces that expectation at the front door, not the back end.
“Legacy app standards don't just slow down the platform. They create data problems that nobody finds until the damage is already done. Tighter listing requirements protect every portal, not just the ones built by careful developers.”
This is part of the same mindset behind updates like pipeline rules for contacts and companies. Cleaner systems, enforced at the structural level, not patched after the fact.
If you're not sure whether your current integrations would pass these standards, or if you're building something and want a second set of eyes before you submit, let's talk. Our team reviews integration architecture across HubSpot portals every week, and we know where the landmines are. Book a strategy call with Sidekick Strategies and we'll help you build a cleaner, more resilient HubSpot stack.
Frequently Asked Questions
Do these new HubSpot Marketplace requirements affect apps already listed?
No. Apps currently listed in the HubSpot Marketplace are not affected by the updated listing requirements. The new standards apply only to new app submissions. However, if an already-listed app applies for certification or recertification, it must meet the latest certification requirements or it will be denied, though it won't be removed from the Marketplace.
What happens to a new app built on HubSpot project version 2025.1 after November 2, 2026?
It won't be approved for listing. Starting November 2, 2026, HubSpot will deny new Marketplace listing submissions from apps built on legacy apps or project versions 2023.1, 2023.2, and 2025.1. Developers must migrate to a currently supported platform version before submitting a new listing after that date.
What's the difference between app cards and legacy CRM cards in HubSpot?
App cards are HubSpot's current UI framework for surfacing third-party app data inside the CRM. Legacy CRM cards are an older method that HubSpot is phasing out. New Marketplace listings must use app cards. Legacy CRM cards create compatibility issues with modern HubSpot records and are no longer accepted in new submissions.
Why does HubSpot now require OAuth v3 for Marketplace apps?
OAuth v3 aligns with current security and API standards on the HubSpot platform. Older OAuth endpoints are less secure and less compatible with modern HubSpot APIs. Requiring v3 reduces authentication vulnerabilities in third-party apps and helps ensure that Marketplace integrations don't create security gaps inside customer portals.
Why does HubSpot require a demo video instead of testing credentials for new listings?
Demo videos and guided walkthroughs let HubSpot reviewers evaluate an app's functionality without needing direct portal access via testing credentials. This approach is more secure, more scalable for HubSpot's review process, and more transparent for potential customers browsing the Marketplace who can now see the app in action before installing it.
How often does HubSpot update its Marketplace certification requirements?
HubSpot updates certification requirements periodically and doesn't follow a fixed public schedule. The company reviews them to maintain quality and security alignment with platform changes. If you're planning a certification or recertification submission, always check the current certification requirements directly in HubSpot's developer documentation rather than relying on older versions.
