Tag Archives: API

Crafting a SaaS API

A SaaS API must (by definition) serve multiple consumers – tenant organizations that desire programmatic access to SaaS provider business capabilities.  Building a SaaS API goes beyond simply adding a tenant key to your API message parser.

Delivering an effective  API Brand  and standing out from the crowd requires personalizing the API experience per user, tenant, developer, or channel.   API provider teams personalize the API experience by accepting diverse message formats or authentication credentials.   Teams also contextualize the API experience by applying personalized service levels, security policies, governance policies, business rules, or data sources.

Creating a SaaS API requires more than run-time message personalization.   API administration, discovery, exploration, and usage portals must adapt, foster a 1-to-1 relationship, and encourage Long Tail adoption. Â Most API Management platforms do not support multi-tenant presentation of API developer portals or API publisher portals.

With WSO2 API Manager 1.4,  deep multi-tenant support enables you to take your entire API portfolio and segment out only the APIs that are applicable to your developer audience.   The multi-tenant API publisher enables API providers to create a customized lists per constituency.   An organization can present an API portal personalized by role or domain. For example, an API portal for partners, suppliers, distributors, or customers.   The API portal may also be contextualized per distribution channel (e.g. retail, wholesale, institutional, government) or API brand.

Because the infrastructure is multi-tenant, you don’t need to deploy multiple API gateways,  API management back-end infrastructure, or purchase multiple software licenses.

When crafting a SaaS API, consider your ability to present a personalized developer portal and segment APIs by audience.   A multi-tenant API Management platform can help API providers create a compelling brand experience.

Swagger with WSO2 API Manager

APIs are often described in JSON, and XML Schema or XML-based client tooling doesn’t work.  Swagger enables developers to describe the API message, produce API schema documentations, and simplify connecting clients to APIs. The overarching goal of Swagger is to enable client and documentation systems to update at the same pace as the server. The documentation of methods, parameters and models are tightly integrated into the server code, allowing APIs to always stay in sync.  WSO2 API Manager now integrates Swagger code.  Swagger spans six distinct GitHub modules:

Continue reading

A New IT Plan: Enterprise DevOps PaaS, APIs, and Ecosystems

Open source PaaS, Open APIs, and Open Ecosystems are accelerating agility, empowering developers, and enabling innovative business strategies.  In a recently published white paper, I describe how adopting a New IT plan can create a responsive IT team.


The path to New IT requires moving away from traditional application platforms, traditional team structure, and traditional information flows.  Responsive IT teams are adapting their infrastructure, processes and tooling to re-invent the application platform and re-think application delivery.  The New IT architecture underlying Responsive IT intelligently incorporates Cloud Platforms, BigData Analytics, Enterprise DevOps, and API first development.


How are you building a pragmatic, open source driven game plan that incorporates New IT approach vectors, Open DevOp PaaS, Open APIs, and Open Ecosystems?

Continue reading

What is an API Management Platform?

Teams use an API Management Platform to increase developer engagement, manage service levels, protect back-end systems, and grow development partnerships and interactions across internal and external teams. When you select an API Management Platform, look for a solution enabling developers to rapidly find, subscribe to, and evaluate the APIs that enterprises make available. The development tools should provide on-demand self-service subscription and collaboration channels, rapidly reducing the time and effort required to integrate and evaluate available API resources.

An API Management Platform contains five architecture components:

Continue reading

Promoting Service Reuse and Maximizing SOA Success

API management complements SOA Governance, drives service reuse, and maximizes Service Oriented Architecture success.  Many development teams publish services, yet struggle to create a service architecture that is widely shared, re-used, and adopted across internal development teams. SOA governance programs often fall far short of encouraging consumer adoption, tracking service consumption, and illustrating business value. Too often, there is little or no insight into service reuse and:

  • How to enable business functionality as an API
  • Who is writing re-usable APIs and services
  • Who is consuming APIs and services
  • How APIs and services are being used

Continue reading

Managing API use case complexity

Will API adoption collapse as vendors push organizations towards managing API use case complexity?  REST and API simplicity has driven interest in the emerging API management market.  API management infrastructure smartly delivers RESTful interfaces, on-demand proxy provisioning, self-service key management, embedded usage tracking, and business focused API monetization    But as vendors search for market messages and competitive advantage, and as customers search for a next-generation SOA middleware to drive legacy service adoption, will the original REST way be lost in use case complexity?

Continue reading