43 Reviews and Ratings
7 Reviews and Ratings
No answers on this topic
Few scenarios 1. For viewing API analytics, I think it is best in the market 2. For earning money via API monetization 3. Securing API 4. Onboarding legacy APIs to provide modern REST endpointsIncentivized
To my opinion Swagger Open Source is a very good tool to quickly produce an api documentation, that how I use it.Swagger can also produce an open api file to generate an api for our application server (Inersystems Iris) but we don't use this functionality for now. We plan to use more Swagger features in the future.Incentivized
Better exception handling with the Raise exception policies help to monitor the flow by setting up the flow conditions.Easy development of a Proxy and APIs with much less tutoring and helps make getting started for new users easy.Very good documentation and blog with details of most common failures and error handling.A very very easy to use console.Incentivized
Produce documentationuser interface to create api definitionreusability of data descriptionIncentivized
Only one user can be active in a proxy at a timeNo version controlProhibited from using JSON.stringify on Apigee objects (tokens)Debugging is difficultUnable to rename or delete policies without bumping revisionWhy would anyone give a js policy one name, display name something else, and script a different name?'Trace' limited to only 20 transactionsUI allows users to add target servers, but users must utilize the api to turn on SSL.I'm sure there's more, they just aren't coming to mind right now.Apigee forgets (expires?) your password at random intervals without notice. Every few weeks, or days, sometimes even three times in one day, I'll attempt to login to Apigee and my password will be 'wrong'. I've reset my password and Apigee still claims it's wrong. I've had to reset my password three times before it finally let me log back in.Incentivized
for me the UI can be more simpletoo many functionnalities when just want to produce doc, can be a separate appA french documentation will be apreciatedIncentivized
I am not the one deciding whether to use apigee or not really. But personally, I would recommend the use of it as developing APIs on it is easy. And as a mediator between backend servers, we could easily modify request and responses in it without touching any backend code while having a centralize gateway to access our backend APIs too.Incentivized
Support has helped us to resolved all the queries and community support was also good.Incentivized
Quite hard to get support, at least on the coding side, when we encounter blockers. But general concerns, they would schedule a call to you for them to get a whole picture of your concern. Albeit in my experience, bad really as they haven't replied about the progress, but otherwise seems to have been fixed.Incentivized
Apigee is the best in the market in terms of API Analytics Apigee is having wonderful Documentation with short videos Security is a major concern and Apigee provides an easily configurable policy to secure API Quota and rate-limit is again very easy to configure on every API basis It provides various policies to transform the response from one form to another form e.g. JSON to XML or XML to JSONIncentivized
We use swagger only to generate the API documentation, for testing the APIs, we use Postman. We don't find an other tools for producing API documentation in web pages and also in pdf files. Postman is a good complement for testing APIs on InterSystems IRIS (a powerful application server and DB manager) which implements these APIs. Incentivized
As a public entity it is hard to say how much ROI we can have. We have yet to create a billing and ROI plan. We are thinking of other ways to create ROI, possibly through data/service barter.Incentivized
Less time to produce our documentationDocumentation can be accessed online, this is a plus for our customers and partnersGreat tools to communicate with other project actorsIncentivized