The success of a digital strategy is no longer measured by how many APIs you build, but by how many are actually consumed. This isn’t just a shift in mindset; it’s a business imperative. To put a number on it, the 2025 MuleSoft Connectivity Benchmark Report shows that APIs now drive 40% of enterprise revenue. That’s a massive chunk of the bottom line resting on whether your code actually gets used.
In an ecosystem where enterprises manage hundreds of assets, “discoverability” has become the true competitive frontier. In fact, Forrester research on API Consumption highlights three critical barriers:
-
Find (Discoverability): APIs often sit in silos where developers cannot easily locate them.
-
Understand (Onboarding/Documentation): Poor documentation and difficult onboarding processes are cited as primary reasons for minimal API reuse.
-
Trust (Reliability): Developers often lack “insightful data on API usage and performance,” making it difficult to trust the API for production workloads.
If a client cannot find, test, and trust your API in minutes, it effectively doesn’t exist.
Over the past few years, I have worked with organisations who proudly told me, “We have hundreds of APIs in production.” But when asked how many of those were actively used by partners, third parties or external developers, that’s usually when the conversation changes. Because the uncomfortable truth is that most organisations don’t have an API problem, they have a consumption problem.
Businesses have invested in API gateways, governance, standards, security. All the right technical building blocks. But from a consumer’s perspective, the experience often looks very different:
-
APIs are difficult to find
-
Documentation is inconsistent
-
Access requires emails, tickets, and waiting
-
Onboarding takes days (sometimes weeks)
-
Confidence in the quality of APIs is low
At that point, the issue is no longer technical. McKinsey points out that the real differentiator today isn’t just the code, it’s the usability and presentation of those APIs.
And this is exactly where Anypoint API Experience Hub starts to make sense.
After several implementations of Anypoint API Experience Hub (AEH), one insight stands out clearly: “A world-class portal is more than just documentation, it is a high-performance storefront for your digital products”
What is AEH and Why a Business Would Actually Need AEH
In simple terms, Anypoint API Experience Hub is a developer portal built on Salesforce Experience Cloud that makes your API catalogue discoverable, testable, and secure for partners, external developers, and internal teams. It connects directly to Anypoint Exchange and presents your APIs as consumable digital products, complete with documentation, interactive consoles, metadata, and branded user experience.
It is not a tool for managing APIs. It is a platform for making them easy to consume. One way I often explain AEH to clients is this:
If Anypoint Exchange is your API warehouse, AEH is the storefront.
Without a storefront, your products technically exist, but nobody knows where they are, how to use them, or whether they can trust them.
This is where the business value becomes very real. In my experience, AEH addresses four core business challenges that traditional API strategies struggle with:
Faster partner onboarding
When partners can discover APIs, try them instantly, and request access without back-and-forth emails, integration timelines drop dramatically. I have seen onboarding that used to take weeks reduce to hours simply because the experience became self-service.
This is especially powerful for industries such as banking, insurance, retail, and government where external integrations are constant.
Less operational load on API teams
API teams often spend a surprising amount of time answering documentation questions, handling access requests manually, explaining how APIs should be used, and supporting onboarding over email or calls.
AEH removes much of this middleman work.
Building trust with partners and developers
A well-presented, consistent, governed portal changes how partners perceive your organisation’s technical maturity.
That perception matters a great deal when you are exposing services to external organisations.
Turning internal APIs into external digital products
Many organisations already have excellent APIs built for internal use. AEH becomes the missing layer that allows those same assets to be exposed externally in a professional and controlled way, without rebuilding anything.
The Essentials: What You Need to Get Started
(image above: A branded AEH developer portal built using Salesforce Experience Builder)
Before you click “Create Portal,” ensure your foundation is solid. These are the non-negotiables for a smooth AEH setup:
-
The Bridge: One linked Production Anypoint Org connected to one Salesforce Org (Experience Cloud).
-
The Passports: External Identity licenses in Salesforce to allow consumers to log in.
-
The Access: Organisation Administrator access in Anypoint Platform and the AEH_Anypoint permission set in Salesforce.
-
The Inventory: High-quality assets in Anypoint Exchange that have passed API Governance checks for security and documentation standards (RAML/OAS) before being published.
Key Benefits of Anypoint API Experience Hub
Rapid Deployment Meets Deep Customisation
(image above: Drag-and-drop customisation without a web development team)
One of AEH’s biggest strengths is speed.
Using the guided setup, you can stand up a fully functional, branded developer portal in hours, not weeks.
You don’t need a specialized web team; because AEH is built on Salesforce Experience Cloud, the customisation goes far beyond theming:
-
Drag-and-drop Experience Builder to build portal with your corporate branding
-
Use Salesforce Lightning components
-
Blogs, announcements, and community forums alongside API documentation
This transforms the portal from a static catalogue to a destination for developers and partners.
From Exchange to Portal: The One-Click Reality
(image above: API metadata in Exchange directly power the experience in the portal)
AEH’s tight integration with Anypoint Exchange is where the platform truly shines.
If your documentation is high-quality in Exchange, it’s instantly high-quality in your portal. AEH automatically syncs:
-
RAML / OAS specifications
-
Markdown documentation
-
“Try It” consoles
No HTML. No CSS. No duplication.
The result? A dramatic reduction in time to first successful API call.
Pro-Tip: Invest early in your Exchange metadata (tags, categories and descriptions). This is what powers the search and filtering in your portal.
The Gatekeeper: Automated API Governance Leveraging Anypoint Platform
(image above: Automated API Governance ensures only secure, well-documented APIs reach the portal)
Exposure to external partners requires a higher standard of quality than internal-only APIs. This is where Anypoint API Governance becomes essential.
-
Enforce Standards at Scale: Instead of manual reviews, use automated rulesets (like OWASP Top 10 or Best Practices) to ensure every API published to the portal meets security and documentation benchmarks.
-
Trust Through Consistency: Governance ensures that every asset in the “storefront” has a consistent look, feel, and security posture, preventing poor-quality metadata from reaching consumers.
Automating the Consumer Lifecycle
(image above: Self-Registration)
(image above: Request API Access)
The goal of a modern portal is to remove the “middleman” from the onboarding process:
-
Self-Service Onboarding: Using AEH with Salesforce Experience Cloud, partner registration becomes a guided “golden path”. Developers can self-register and gain instant access.
-
Automated Offboarding: “Zombie credentials” are a real risk. Salesforce Flows can automatically revoke client applications when partner contracts expire.
Enterprise SSO
(image above: Single Sign-On using Microsoft)
One of AEH’s strongest enterprise capabilities is Single Sign-On (SSO).
-
Enterprise-Grade SSO Support: Because AEH is built on Salesforce Experience Cloud, it supports SAML and OpenID Connect integrations with providers such as Okta, Azure AD, and Ping.
-
Unified Identity Across Ecosystems: Internal users, partners, and external developers can authenticate using their enterprise identities, reducing friction and improving security posture.
Important caveat: SSO configuration and identity orchestration are managed in Salesforce, because AEH is build on Salesforce Experience Cloud.
Lessons Learned: Navigating AEH Limitations
AEH is a strong accelerator but it’s important to understand its intentional platform constraints before scaling adoption. These are not blockers. They are architectural considerations I now discuss with every client before we begin. Here are the “lessons from the trenches”:
One Organisation, One Portal by Design
One of the first things I check is the client’s architecture. AEH enforces a strict 1:1 mapping between your Anypoint and Salesforce organisations. For enterprises running multiple Anypoint orgs across regions or business units, this becomes an early architectural conversation. The key decision is whether to consolidate assets into a single strategic org or plan for multiple portals. When addressed upfront, this becomes a design choice rather than a surprise later.
Plan for Scale from Day One
By default, AEH is configured for smaller catalogue. To host more than 350 APIs in existing portals (or 1000 APIs in newer portals), you must manually enable the scalability option to reach a 7,000 API limit. Enabling the scalability option for Anypoint Experience Hub does not typically incur a direct license fee for the feature itself, but it can trigger secondary costs based on your Anypoint Platform subscription and Salesforce integration requirements. This change cannot be reverted, making early capacity planning critical.
No Native Admin Notifications for User Registration
AEH does not natively notify administrators when new users register. I have sat in meetings where stakeholders asked, “How do we know that a new customer registered on the portal?” and the answer was that this requires additional configuration rather than an out-of-the-box feature. While this can be addressed using Salesforce Flows or notifications, it is something you want to include in your setup checklist to ensure operational visibility from day one.
Customisation Requires Salesforce Expertise
AEH makes portal creation fast, but meaningful customisation relies on Salesforce Experience Cloud, Lightning components, and Flows. Teams that recognise this early and involve Salesforce expertise unlock far more value from the platform than those expecting a simple theming exercise.
The Warehouse Rules the Storefront
I tell my clients Governance isn’t an option; it’s the prerequisite. AEH is only as good as your Anypoint Exchange hygiene. If your specifications are messy or your descriptions are cryptic in Exchange, they will look twice as bad when published to a shiny portal. If an asset hasn’t passed a quality check in the warehouse, it has no business being in the front window.
Limited Control Over API Visibility Rules
Within the portal, authenticated users can generally see the full API catalogue. Fine-grained visibility at the UI level is limited. This encourages a best practice where trust is enforced through API policies and security at runtime rather than relying on what users can or cannot see in the catalogue.
Bring Your Own Analytics for Deeper Insight
While AEH provides basic usage insights, but deeper journey tracking requires integration with Anypoint Monitoring, Salesforce reports, or third-party analytics. For organisations serious about measuring developer experience, this becomes part of the broader tooling strategy.
The Access Journey Is Structured
The access flow follows a defined pattern: discover an API, create an application, then request access. This works very well for most scenarios, but highly bespoke onboarding journeys may require custom development rather than configuration changes.
Beware of Application Sprawl
Finally, keep an eye on your client applications. Any authenticated user can create a client application, and AEH does not automatically retire unused ones. A small amount of Salesforce automation or governance process goes a long way in preventing application sprawl and keeping your environment tidy.
The Bottom Line
Anypoint API Experience Hub is the fastest way to turn Exchange assets into consumable digital products.
Long-term success depends on:
-
Designing around platform constraints
-
Leveraging MuleSoft API Governance capabilities to automate hygiene and maintain quality
-
Planning for scale and Salesforce dependencies from Day 1
Used within its guardrails, AEH becomes a powerful driver of API adoption, not just another portal.
