RepreZen API Studio Reviews

This tool has a basket of generating outputs that make communications between my technical team and 3rd parties clear and concise. From JSON to YAML conversions, various HTML pretty formats and ways to express examples, just about every level of actor will find an output format or 2 useful.

The other very valuable feature is the smart auto-completion / suggestion. This feature alone has cut the specification development time and also reinforces specification capability. It's particularly useful when associating external files via reference.

I'd like to see a graphical object perspective that could show impacts and results

I tried about a half dozen open API editors, RepreZen API Studio is by far the best I have come across and well worth the price

I have taken a monolithic application and converted it to a microservices architecture. I use RepreZen API Studio to develop the communication specifications between the services. I also use this product to create schema specifications of some internal memory components.

The easy-to-use interface and context-sensitive editor.

No real dislikes. Product did what I had hoped it would.

Developing an API for a client. We wanted to use a top-down design, and RepreZen helped us accomplish that.

I enjoy the fact that errors are flagged and easily resolved through visual queues. In addition, Reprezen API Studio makes creating and managing OpenAPI specification files easy

The support of the product is always prompt and thorough.

Nothing.

The only thing that I would like is to be able to select a definition or path and navigate to that definition - much like the Java perspective allows for methods and classes.

Just get Reprezen API Studio. It is all you need to OpenAPI specification development and management

We have a large API and the OpenAPI (swagger) specification files needed to be modularized. swagger-codegen could not normalize all of our specification files. We were unable to use swagger-editor or swagger-ui unless the specification file was one file.

Reprezen offers an awesome user experience not only in editing and creating our OpenAPI spec, but also in visualizing it through the swagger-ui view.

It is the best OpenAPI editing tool that I have used.

We tried everything we could find -- from free to really pricey, and all the usual editor modes and add-ins -- to design and deploy the API for our new SaaS product. Everything came up short, and I mean really short. If you've tried working with Swagger/OpenAPI YAML in an IDE or editor, then you've felt the pain. RepreZen makes it so easy to get your OpenAPI definition just right without wrestling with the fiddly little details of YAML syntax. I wish we found this product sooner. Defining our APIs for AWS API Gateway got so much easier. What a huge time saver. And RepreZen customer service is absolutely amazing, among the best I've ever received.

Nothing. Well, I wish I'd found this product sooner. I wasted more days than I care to admit on stuff that RepreZen just "handles".

Try lots of products. Give all the programming editors a shot. We tried IntelliJ IDEA as well as Atom with YAML mode. Mess with swagger.io. You'll learn quickly that this is the best solution for creating OpenAPI definitions. Or you could just save yourself the pain.

OpenAPI design for AWS API Gateway REST service implementation.

Consider RepreZen API Studio, which includes a Swagger editor that fulfills the need for validation and multi-file reference while offering the following benefit for workflow: You can now request a documenter to describe a single REST API path like /company/orders.json or a collection of such paths; and the documenter's work can be isolated in one or more files, reducing the complexity of assigning and reviewing the descriptions.

In addition, RepreZen is developing a generated output that is superior to the traditional Swagger output when your need is documentation alone rather than a combination of documentation and interactivity. This generated output displays the request payload and the response; and within each of those definitions, the reader sees the component fields, their types, and a description of each. All descriptions can be as complex as allowed by Markdown. You also can create a traditional Swagger output.

RepreZen API Studio is still in development.

To confirm what I've written, download a free copy at http://reprezen.com/swagger-tools .

Am documenting a long-standing API that is used by integrators to fulfill new opportunities.

Enterprise modeling focused - flexibility, ability to generate code from Rapid-ML and/or Swagger based models.

Eclipse IDE is challenging and not as intuitive as would like

API First modeling - taking models to code - has allowed for the separation of roles - ie. data governance can work on the canonical data models and architects, team leads can focus on the API Design