webMethods API Gateway Overview

webMethods API Gateway is the #13 ranked solution in our list of top API Management tools. It is most often compared to webMethods.io Integration: webMethods API Gateway vs webMethods.io Integration

What is webMethods API Gateway?

Once your APIs are “out there,” hackers have a “way in” to your business. Lock that door! Protect your data, applications—even your company’s reputation—with robust API runtime security. The right API gateway will keep out wrong-doers and welcome only authorized consumers.

With cybercrime costs surging to $2 trillion by 2019, look for the most impermeable API gateway you can find. You’ll need basic security features, like authentication, authorization, digital encryption and digital signatures. You’ll get that with Software AG’s end-to-end API management solution—and another lock on top.

Our webMethods API Gateway uses reverse invoke, or inside-out, service invocations. This protective technique reduces the need to open holes in your firewall. It’s one more way we help you lock down your APIs—and protect your business from malicious attacks.

webMethods API Gateway Buyer's Guide

Download the webMethods API Gateway Buyer's Guide including reviews and more. Updated: July 2021

webMethods API Gateway Video

Pricing Advice

What users are saying about webMethods API Gateway pricing:
  • "I do see a lack of capabilities inside of the monetization area for them. They have a cloud infrastructure that is pay per use type of a thing. If you already use 1,000 transactions per se, then you can be charged and billed. I see room for improvement there for their side on that particular capability of the monetization."
  • "This is not a cheap solution but, compared to other products such as those offered by IBM, the pricing is similar."

Filter Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Rully Feranata
Enterprise Architect at PT Bank Mandiri (Persero) Tbk.
Real User
Top 5Leaderboard
We developed several services in the cloud using a sandbox environment for our last hackathon

What is our primary use case?

We have an open banking initiative in Indonesia. We are mandated by a regulator's bank in Indonesia to open up our services to other institutions, not only banks, but also financial technology (FinTech) companies and startups as well as eCommerce or other industries. Thereby, they can consume banking services through an API, such as our funds transfers, mobile banking services, or a bill payment, like electricity, water bills, college, and so on, through an API to their applications. It is not obligatory that you need to download our mobile banking in order to do these transactions, but you… more »

Pros and Cons

  • "Within the new version, webMethods API Gateway gives us an end-to-end lifecycle from the creation of the API up into the development, deployment, and promotion into production/live. The current end-to-end lifecycle of the API gives us enough authority and governance of the API. We know what are currently live services, what is in the testing stage of development, and what version that has been commissioned. So, the full life cycle itself gives us full authority and governance of the API."
  • "With performance, there is room for improvement in regards to if we would like to put another extra layer of security on it, such as SSL. This is affecting their performance quite significantly. They need to improve the process of managing the SSL and other things inside their solutions, so there will not be quite such a significant impact to the performance."

What other advice do I have?

In every implementation of webMethods API Gateway, I strongly suggest that you need good API governance. webMethods has their API governance all built inside of your license. It is a continuation between the services using the webMethods Integration Server and webMethods API Gateway, exposing those services into the outside world. You need to have good governance for that. I would rate this solution an eight (out of 10).
Dries Vanmarcke
Technical Architect at Colruyt
Real User
Top 5Leaderboard
Secure, good monitoring capabilities, and the automation gives us a competitive advantage

What is our primary use case?

This solution is primarily used for protecting our APIs and web services. All of our APIs are exposed to the outside world, so our internal network is protected by the API gateway. Our landscape inside the company is also divided into different domains and if you go from one domain to another domain, we also want the APIs to be protected. We have two servers with an API gateway and a load balancer in front of it. We also use this solution for monitoring, to know how many transactions we have had and who is using our API. These are the runtime capabilities. Another thing we use this product for… more »

Pros and Cons

  • "This solution has given us a competitive advantage because we have better automation and insight."
  • "With respect to the API gateway, the runtime component, the stability after a new release is something that can be improved."

What other advice do I have?

This solution provides a fully customizable portal that has built-in testing capabilities, although we haven't implemented it yet. This is something that we are planning to do within the next couple of months. My advice for anybody who is implementing this product is to involve consultants who are familiar with it because they can help you to best set it up. Also, think about the process and steps in your governance because this is a workflow and you want to be sure that it follows the procedures that you have in place. Overall, I'm happy with the product. I would rate this solution an eight…
Learn what your peers think about webMethods API Gateway. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
523,535 professionals have used our research since 2012.
Ram Kanumuri
Vice President - Digital Integration at Kellton Tech Solutions Limited
Real User
Top 5Leaderboard
Easy to set up with runtime metrics and offers good insights into the operations of the API

What is our primary use case?

The API Gateway and Portal go together. It's not one or the other. Essentially they're just leveraged for overall enterprise API management facilities, being able to go on the API development life cycle, being able to go on the API run time, API monetization, things like that. Usually, most organizations, most of our customers use APIs to supplement other architectures, typically microservices-based application architecture, and SaaS integration etc.

Pros and Cons

  • "The cloud version of the solution is very easy to set up."
  • "In terms of improvements, maybe on the API monetization side, having users able to create separate consumption plans and throttle all those consumption plans towards the run time could be better."

What other advice do I have?

We are partners with Software AG. We've been a partner for more than 20 years now. I'm a consultant. I work with a consulting company. I'm familiar with API Gateway, API Portal, and Active Transfer. The API Portal and Gateway form the layer of API management, however, usually, API management does not go on its own. There's typically some level of an integration layer behind it as well. Either a customer is applying an API management layer on top of an existing integration layer, or, if not, a customer is starting fresh and has to apply both layers subsequently, or consecutively, kind of like…