Visual Integrator BLog

Where the API Experts discuss the latest in

API’s & Microservices 

Latest Post 

Best Practices for an API Portal

Best Practices for an API Portal

Listed below is a list of metrics to manage Microservices and API initiatives



With the adoption of APIs into organizations, it’s clear many desire to enable self-service capabilities for their API consumers. The best way to achieve this with today’s technology, is through an API portal.

Below are some important Best Practices for APIs entering an API Portal. I created a 58 point checklist for APIs to follow to govern entering an API Portal, but below are some immediate Best Practices. Please email me if you would like a copy of the API Portal Checklist, or if you would like me to present it to your team.

1) Make sure API Providers have clearly defined the functional and technical definition of the API. Sounds trivial, but its important.

2) Adopt Swagger and Open API spec, so all APIs can be easily and consistently managed in the portal

3) Define your Security Model for internal and external facing APIs. Will it just be Client ID/Secret or will you have an OAUTH2 Policy?

4) Mandate a Data Dictionary before APIs enter the portal. Consumers need to understand field level definitions.

5) Understand if the APIs are for Systems of Record vs. Intermediary Systems.

6) Identify sensitive data, so it can be properly protected through security and encryption tehcniques.

7) API Providers must have a TEST environment for your portal to have a “Try it Now” feature.

8) API Providers must share their version control process.

9) Also, their Change Management (and communication) process.

10) How are the API providers doing logging, auditing, and Analytics? Please have them share this before entering the Portal.

11) Do they have SLA’s on their APIs for response times and availability?

12) What about constraints on # of requests, concurrent consumers

13) What is the API provider’s Operations and Support model?

14) How does API providers alert consumers?

15) What are the API Providers quality assurance techniques? How does the Portal know the API has been tested for functionality and performance? Can the API Provider share their testing results?


Jordan Braunstein, CTO

How to Measure Microservices and API Success

How to Measure Microservices and API Success

Listed below is a list of metrics to manage Microservices and API initiatives



  1. Self Service Enablement. Providers and Consumers adhere to the policies, practices, processes, and standards created by the Microservices/API Marketplace teams. Once they are familiar with such approaches, they can be self-serving to follow the processes with minimal interaction. A measure of success shall be how Providers and Consumers can effectively complete their interactions with minimal intervention.

2. Adoption of the Microservices and API Marketplace.This can be measured in the # of APIs published, # of Consumers total and for specific APIs, # of API calls.

3. Minimalization of Defects, Issues, Complaints.By establishing processes and quality control mechanisms, a measure of success will be keeping the API defects, issues, and complaints low from API Consumers.

4. Project Implementation Speed:By using Microservices and APIs from the API Marketplace, project teams can implement their business processes quicker by leveraging an existing service from the marketplace, instead of recreating one.

5. Lower Total Cost of Ownership:For the same reason as described in #4, by re-using existing Microservices assets and services that are discoverable in the marketplace, instead of recreating new ones, lowers the total cost since it lowers implementation and maintenance of duplicate assets.

Jordan Braunstein, CTO

Past Posts 

No Results Found

The page you requested could not be found. Try refining your search, or use the navigation above to locate the post.

Want more?

Contact us to Discuss your API & Microservices Strategy Today

Contact Us