TrustRadius
IBM API management enables creation and management of web application programming interfaces (API).IBM API Management EvaluationIBM API Management is used for API lifecycle management - for creating, managing and securing APIs. It is an extension of the DataPower gateway used to manage cross-functional APIs and services. Used as an enterprise tool for socializing APIs through its discoverability and cataloging features. Performance, scaling and operational statistics are used to help identify hiccups or trends in service disruption.,Import APIs - We have an existing inventory of APIs and services, so having an easy import process was required. IBM provides the ability to import Swagger so the process was quick and easy. Service Offerings - Can create plans to control various model offerings for varying clients depending on the need. You are not locked into a tier structure and can customize if a need arises. API Usage - visibility into the use of an API with a wealth of reporting information allows you to support an API from a production use to trending and forecasting any future growth.,Troubleshooting deployment pipeline - identifying issues with your api based on restrictions through a deployment pipeline is difficult. If a quality assurance environment is less stringent than a production environment, making sure your api is accessible and configured appropriately is tough. Code level scripting is limited to javascript and xslt. so if any complex fanning needs to occur, you are limited in tooling. Administration is more cumbersome than it needs to be. There are roles/profiles that are defined, but to use a group email for the approval or use of an api needs to managed better. A more thorough thought process needs to be defined - which I think IBM is tackling as an improvement.,8,Centralizing on an API management platform was imperative. Being able to support SOAP UIs as well as REST APIs was required. Because of the tooling, service inventory and provisioning can be managed - regardless of the pricing and cost structures are used. Constructing plans that provide tiering options based on rate limits help in onboarding new consumers. The lesser cost in onboarding through an API gateway outweighs the cost of modifying/configuring an API to handle multiple clients. Defining guidance and onboarding practices while rolling out the product also helps in the adoption, reference architecture, and governance that can save your company money.,Apigee
Unspecified
IBM API Management
22 Ratings
Score 6.7 out of 101
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>TRScore

IBM API Management Reviews

IBM API Management
22 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow'>trScore algorithm: Learn more.</a>
Score 6.7 out of 101
Show Filters 
Hide Filters 
Filter 22 vetted IBM API Management reviews and ratings
Clear all filters
Overall Rating
Reviewer's Company Size
Last Updated
By Topic
Industry
Department
Experience
Job Type
Role
Reviews (1-1 of 1)
  Vendors can't alter or remove reviews. Here's why.
Brent Heezen profile photo
July 09, 2018

User Review: "IBM API Management Evaluation"

Score 8 out of 10
Vetted Review
Verified User
Review Source
IBM API Management is used for API lifecycle management - for creating, managing and securing APIs. It is an extension of the DataPower gateway used to manage cross-functional APIs and services. Used as an enterprise tool for socializing APIs through its discoverability and cataloging features. Performance, scaling and operational statistics are used to help identify hiccups or trends in service disruption.
  • Import APIs - We have an existing inventory of APIs and services, so having an easy import process was required. IBM provides the ability to import Swagger so the process was quick and easy.
  • Service Offerings - Can create plans to control various model offerings for varying clients depending on the need. You are not locked into a tier structure and can customize if a need arises.
  • API Usage - visibility into the use of an API with a wealth of reporting information allows you to support an API from a production use to trending and forecasting any future growth.
  • Troubleshooting deployment pipeline - identifying issues with your api based on restrictions through a deployment pipeline is difficult. If a quality assurance environment is less stringent than a production environment, making sure your api is accessible and configured appropriately is tough.
  • Code level scripting is limited to javascript and xslt. so if any complex fanning needs to occur, you are limited in tooling.
  • Administration is more cumbersome than it needs to be. There are roles/profiles that are defined, but to use a group email for the approval or use of an api needs to managed better. A more thorough thought process needs to be defined - which I think IBM is tackling as an improvement.
If you are truly using IBM API Management for an API gateway, you will be ok. if you start trying to build custom scripts to transform messages complex in nature, it will soon become unmanageable.
Read Brent Heezen's full review

IBM API Management Scorecard Summary

Feature Scorecard Summary

API access control (1)
8
Rate limits and usage policies (1)
9
API usage data (1)
9
API user onboarding (1)
7
API versioning (1)
7
API monitoring and logging (1)
8

About IBM API Management

IBM API management enables creation and management of web application programming interfaces (API).
Categories:  API Management

IBM API Management Competitors

IBM API Management Technical Details

Operating Systems: Unspecified
Mobile Application:No