Dmitry Sotnikov is Vice President of Cloud solutions at WSO2.
Prior to WSO2, Dmitry worked at Quest Software (now part of Dell) as Director of Cloud Solutions, and later co-founded Jelastic PaaS and led Jelastic’s sales, marketing, customer and partner relationships. Dmitry has been a featured speaker at multiple industry events including Microsoft TechEd, VMware VMWorld, Parallels Summit, Quest Innovate, and Technology Experts Conference (TEC).
API programs are key to building the ecosystem around your technology. Your developer portal and APIs represent who you are to your partners and customers. This is why branding is very important part of API efforts.
Branding for API programs consist of:
Your own custom URLs for developer portal and APIs,
Your logos, style, look and feel of the developer portal.
With the addition of custom URL functionality, WSO2 API Cloud now supports both kinds of customization.
1. Custom URL
By default, API Store for your subscribers gets a URL that looks like https://api.cloud.wso2.com/store/?tenant=[your organization id], and the APIs themselves start with https://gateway.api.cloud.wso2.com:8243/t/[your organization id]/.
My guess, is that instead, you would like a fully branded experience with API Store being available at something like http://developers.mycompany.com and APIs at http://apis.mycompany.com.
Now all you need to do get there is:
Come up with the nice URLs for both the API Store and the API gateway (and purchase the domain if you have not done so),
Purchase SSL certificates for both domains (this is required because both portal and APIs themselves need to be accessed via HTTPS),
In your domain registrar’s DNS panel, create CNAME records pointing to customdns.api.cloud.wso2.com for APIs themselves, and customdns.api.cloud.wso2.com for the developer portal,
In WSO2 API Cloud, click the Custom URL menu and follow the configuration wizard.
WSO2 API Cloud has all you need for successful API program. This means that besides just publishing your APIs and opening subscriber portal, you need to have detailed analytics reports to see the actual subscriber behavior and be able to block the subscriptions that do not comply with your policies.
We have published a couple of quick demos to show how this works.
Some of our out-of-box API analytics reports:
And here’s a quick video of how individual subscription can be easily located and suspended:
With the latest updates to WSO2 API Cloud, we have made publishing and subscribing to APIs even easier!
Published APIs now just work out of box including interactive API Console (you no longer have to enable OPTIONS method for your APIs or edit Swagger file) – so the number of clicks to get your API published went down dramatically and the process became extremely straight-forward:
In subscriber portal (API Store) things got simpler as well. Interactive API Console no longer requires you to provide OAuth key manually and just grabs it from your configuration automatically. It also shows you various invocation and response details including the sample Curl command for your API call:
With these (and many smaller) changes and improvements, your API programs are now even more attractive and easier to implement.
OAuth2 has become the industry standard for secure API access, and is the default security mechanism that you get for your API subscribers in WSO2 API Cloud. API Cloud fully automates OAuth key generation and management.
However, there are circumstances when you might want to temporarily have your APIs available with no security required. For example, this might be the way you decide to launch them initially while you are still on the prototype phase.
WSO2 API Cloud gives you two ways of achieving this:
By publishing your API as Prototype, or
By setting required resource authentication level to None.
Publishing as Prototype
Prototypes are different from common published APIs because they are meant to run your ideas across your community to quickly collect feedback.
Either way, they require no subscription. Your users will be able to give them a try without having to subscribe to them.
To publish an API as prototype:
Pick Prototype on the second step of API creation (Implement),
Click Deploy as Prototype.
The API will appear on the Prototypes tab of API Store and will not require authentication for access.
Authentication Type: None
You can also remove authentication requirements for regular managed APIs. This is useful when you want to still have the API listed on the API Store home screen and/or when you want to disable authentication requirement for individual resources of an API.
For that, go all the way till the last (Manage) step of API creation, and then change Authentication Type to None in the drop down next to each API resource at the bottom of the screen:
WSO2 App Cloud is the most comprehensive platform-as-a-service (PaaS) in the market covering the whole application lifecycle from issue and task tracking, to Git source code repository, to cloud IDE, databases, lifecycle management, and more.
Good news! We have just finished upgrading WSO2 API Cloud to the latest codebase of WSO2 API Manager (1.9) – which brings us the latest features and fixes.
The biggest improvement is full Swagger 2.0 support. Swagger is the industry standard for API definitions and this is what API Cloud is using natively as well.
You can not just import or export the Swagger definitions, but also edit your API in full-featured Swagger editor with intellisense tooltips, syntax checks, and so on. Simply click Edit Source on the first step of API editing:
And you get the full power of Swagger at your disposal:
There are many other improvements and fixes, and we will be now re-releasing our tutorial videos and publishing new blog posts covering the exciting new functionality. Stay tuned!