Coming October 25: PeerSpot Awards will be announced! Learn more

webMethods API Portal OverviewUNIXBusinessApplication

webMethods API Portal is #25 ranked solution in top API Management tools. PeerSpot users give webMethods API Portal an average rating of 7.0 out of 10. webMethods API Portal is most commonly compared to Amazon API Gateway: webMethods API Portal vs Amazon API Gateway. webMethods API Portal is popular among the large enterprise segment, accounting for 73% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a computer software company, accounting for 22% of all views.
Buyer's Guide

Download the API Management Buyer's Guide including reviews and more. Updated: September 2022

What is webMethods API Portal?

Software AG’s webMethods API-Portal provides a comprehensive solution that allows the developer community to find, learn about, discuss and test your APIs. This API portal not only exposes API documentation to developers inside and outside of your organization but also manages the developer on-boarding process and lets developers use exposed APIs for new and creative uses.

Software AG’s new API portal offer significant benefits for companies working on API monetization, including:

-An intuitive user interface and highly customizable “look and feel”
-A single solution for both external and internal developers
-Analytics at the API portal to help you better understand your users
-Strong API security through the use of API keys and OAuth2 credentials support
-Seamless integration with other webMethods components, including CentraSite, Software -
AG’s SOA governance and SOA life-cycle management solution

webMethods API Portal Video

webMethods API Portal Pricing Advice

What users are saying about webMethods API Portal pricing:
"Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission."

webMethods API Portal 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
Ram Kanumuri - PeerSpot reviewer
Vice President - Digital Integration at Kellton Tech Solutions Limited
Real User
Top 5Leaderboard
Stable, with good technical support, but the on-premises version can be difficult to set up
Pros and Cons
  • "We have found the pricing of the solution to be fair."
  • "The on-premises setup can be difficult."

What is our primary use case?

The API Gateway and the 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 so on.

What is most valuable?

On the portal, the user management and the API life cycle management are definitely robust. 

They have nominal features for API. They have a self-serve API portal as well. That means consumers for APIs can come onto the portal and learn about various APIs that they can put into the consumption model. 

The initial setup of the cloud version of the solution is very easy.

The solution can scale.

The product is quite stable.

Technical support is responsive and quite helpful.

We have found the pricing of the solution to be fair.

What needs improvement?

On the API monetization side, being able to create separate consumption plans and throttle all those consumption plans towards the run time. Those are abilities that might need some improvements.

The on-premises setup can be difficult.

For how long have I used the solution?

I've been dealing with the solution over the last three or so years at least.

Buyer's Guide
API Management
September 2022
Find out what your peers are saying about Software AG, Amazon, IBM and others in API Management. Updated: September 2022.
633,184 professionals have used our research since 2012.

What do I think about the stability of the solution?

The stability and performance are definitely very good. 3G really comes strong on an enterprise-scale in terms of stability and performance. It doesn't crash or freeze. There are no bugs or glitches.

What do I think about the scalability of the solution?

The solution can scale quite well. A company that needs to scale can do so.

API management is all about internally leveraging the software development life cycle, across various domains. Typically, most customers, when they adopt API management, they are delivering it for their entire IT software development organization, not just the integration team. The application team and the database team and so on will also use it. Everybody will be on board. Sometimes we have seen customers onboard about 60, 70 developers and then maybe a few additional external consumers. However, we also see some customers with very small teams of around 10 people. It works well for both.

How are customer service and support?

We've dealt with technical support in the past. There's always that possibility, especially with newer versions, that we might run into some technical issues. However, tech support and issue management are both pretty straightforward. 

You can now create a ticket on an issue with the portal on Software AG through Software AG's support portal. They respond within a day, and at least try to resolve the issue. Sometimes the issues might need a product or a quote fix, which might take a day or two. Otherwise, they might be able to look through the knowledge base and give us a solution immediately. In general, they have a decent response time and a decent quality of service. We're satisfied. 

How was the initial setup?

In terms of setting up the solution, there are two ways. The first is that you can have an on-premise license and set up this conference yourself. That can be a little complex depending on what is the overall deployment architecture that is needed. On the other side, webMethods API also comes in a cloud form, the webMethods.io, and that is just a subscription. Most of our customers can just subscribe to it and they don't really have to worry about the setup. Everything is already pre-set.

Usually, while the on-premises setup is fairly complex, we don't really require people to be continuously monitoring it once it's launched. The setup itself might take less than a week or two, depending on the size of the enrollment. In terms of maintenance, unless there's a lot of APIs subsequently developed and running, you don't really have too much. Once the customer starts developing a lot of APIs and puts a lot of those APIs into production, that's what will contribute to the support and monitoring needs of the team. Typically one person can handle deployment and maintenance. Of course, the cloud doesn't really require the same amount of work. 

What's my experience with pricing, setup cost, and licensing?

The pricing fluctuates. I don't have the numbers with me, however, I can say that they're not the cheapest in the market, and they're not the most expensive either. They fall right in the middle, and they're priced right for their capabilities and the quality of service as well as the stability and performance on offer. They're well priced for their general offering.

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 an IT consultant. We are a consulting company, most of my teams are certified in Software AG technology, and we've worked for a lot of customers leveraging that technology.

We typically deal with the most up-to-date versions of the solution, although occasionally, one or two might be a version behind.

A lot of 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. It's kind of like creating an API management layer, and a hybrid integration layer. Both go together, especially in data integration, or in application integration and cloud application integration.

Overall, I would rate the solution at a seven out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Integration Analyst at a paper AND forest products with 5,001-10,000 employees
Real User
Top 10
Good for connecting systems and retrieving data, but doesn't have a predefined service for our use case and is expensive
Pros and Cons
  • "It is good for communicating between the systems and for publishing and subscribing. We can easily retrieve data. It is good in terms of troubleshooting and other things."
  • "Some of the things that we use cannot be done in this solution. For these things, we have to either use a Java service or a util service. There is no predefined or existing service that we can use. So, we have to work on the util service and write on top of it. Its price can also be better. It is pretty costly because they charge us for each transmission."

What is our primary use case?

We use it for our ERP systems. It is a middleware tool that we use to connect two systems and the outside partners.

What is most valuable?

It is good for communicating between the systems and for publishing and subscribing. We can easily retrieve data. It is good in terms of troubleshooting and other things.

What needs improvement?

Some of the things that we use cannot be done in this solution. For these things, we have to either use a Java service or a util service. There is no predefined or existing service that we can use. So, we have to work on the util service and write on top of it.

Its price can also be better. It is pretty costly because they charge us for each transmission.

For how long have I used the solution?

I have been using this solution for four years.

What do I think about the stability of the solution?

There have not been any stability issues.

What do I think about the scalability of the solution?

It is not that much scalable. We have around ten people who are using this solution. Only the integration team uses this solution. Other teams have the ERP system.

How are customer service and technical support?

It is easy to get support. When we posted a query or some issues, they got back to us. They are responsive and knowledgeable.

How was the initial setup?

It is straightforward and easy. You have the documentation, which is easy to follow.

What's my experience with pricing, setup cost, and licensing?

Based on our team discussions and feedback, it is pretty costly because they charge us for each transmission.

What other advice do I have?

I would rate webMethods API Portal a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user