Multi-domain governance and openness: what’s new in ApiShare

The new ApiShare 1.11 release marks a major step towards more flexible governance and greater API openness. In today’s digital landscape, where architectures are increasingly distributed and organizations more complex, the new features address real-world challenges faced by enterprises managing APIs at scale.

Domain-based administrative roles

As APIs become central to enterprise strategies, organizations must manage increasingly diverse areas of responsibility — not just publishing services, but also handling user access, technical configurations, and governance rules consistently and securely.

Until now, this complexity often led to overlapping roles and permissions, with administrators operating across overly broad areas or under unclear policies. The result? risks of unauthorized access, conflicting responsibilities, and slower development and release processes.

With ApiShare 1.11, it is now possible to assign separate administrative roles for each domain within the same organization. In practice, each area can rely on dedicated managers with distinct and clearly defined permissions. For example:

• managing external users or partners who can browse the catalog and consume available APIs;

• managing technical configurations, such as environments, API publishing domains, or SMTP servers for notifications;

• managing governance configurations, including processes, roles, and internal notifications.

This approach not only strengthens security but also improves collaboration between teams, reducing conflict areas and making governance more transparent.

For enterprises, this translates into:

• the ability to scale more easily, as the platform grows alongside organizational complexity;

• simplified audit and compliance, thanks to clearer and more traceable rules;

• increased productivity, with teams focusing on their domain without interfering with others.

Customizable public landing page

Visibility is another key challenge. APIs may be powerful, but without a proper gateway, they remain hidden from those who could use them. In many cases, documentation and catalogs are locked behind registration forms, limiting adoption and slowing down onboarding.

The new customizable public landing page changes the game. Organizations can now provide an open, accessible showcase that acts as a digital front door to their API ecosystem:

• selected documentation can be made visible from the start, giving potential users a clear preview;

• the product catalog can be structured as a discoverable ecosystem, with straightforward navigation paths;

• external developers, partners, and even customers can explore APIs independently, without barriers.

This dual impact makes APIs not only more discoverable but also more appealing as digital products promoted to the outside world, strengthening business opportunities and community engagement.

Strengthened security and authentication

Greater openness also requires stronger protection. That’s why ApiShare 1.11 introduces two key enhancements:

• dynamic credential issuance via external Identity Providers, simplifying onboarding while maintaining central control;

• extension of the KeySet management capability, allowing greater flexibility and security in controlling the period during which the keys granted for API access remain visible to consumers.

Together, these features enable faster, safer integrations and ensure that APIs can operate securely in increasingly distributed ecosystems.

Conclusion

With these innovations, ApiShare evolves into a governance platform capable of supporting multiple domains within a single organization while also opening up to external audiences.
Enterprises adopting these capabilities will combine control with openness, efficiency with visibility, and transform their APIs into key enablers of digital growth.