G2

Vikash K.

SWE

Insurance

Mid-Market (51-1000 emp.)

Originally submitted 11/10/2026

"Centralizes our OpenAPI 3.1 and AsyncAPI specs with shared Domains"

4/5

What do you like best about Swagger Studio?

In our claims engineering team, we maintain multiple Python and FastAPI backend services alongside a React and Node.js adjuster web portal. Before adopting Swagger Studio, developers frequently updated Pydantic request or response models in one backend repo without updating shared documentation, which caused unexpected breaking changes for the frontend team and webhook integrations. Moving our contract design into Swagger Studio gave us a single workspace to author and version specifications like our hcc-claims-pricing-api in OpenAPI 3.1 alongside our asynchronous event payloads before writing implementation code. What helps our day-to-day workflow most is having the dark YAML Code editor, the visual Form editor, and Diff Mode right next to the live Swagger UI and Elements preview panes. When defining endpoints like getClaimLineItems or attachClaimReceipt and referencing shared schema models such as ClaimLineItem, ReceiptAttachment, DepreciationSchedule, and ActualCashValueSummary, the bottom Validation panel catches missing operationId fields, parameter mismatches, and Spectral style violations in real time before a pull request is ever opened. Review collected by and hosted on G2.com.

What do you dislike about Swagger Studio?

While reusable Domains and GitHub Sync save a lot of manual work, how external domain references behave during repository sync created extra scripting for our CI/CD pipeline. Unlike exporting a resolved bundle, syncing specs that reference private SwaggerHub domain URLs pushes unresolved reference strings into GitHub, which local FastAPI test runners and external gateway linters cannot resolve without an extra API build step to pull the bundled JSON file. We also noticed a couple of quirks when managing OpenAPI 3.1 specifications in the editor. Updating the version field inside the YAML info block (for example from 1.0.0 to 1.2.0) does not automatically bump the Swagger Studio version dropdown until you explicitly click Create New Version in the top bar, which can confuse developers who edit the YAML directly. Additionally, while the Codegen menu is available in the toolbar, its generated Python server stubs do not match our async FastAPI and Pydantic v2 structure, and editing very large YAML specs with real-time validation active can make the browser editor lag. Review collected by and hosted on G2.com.

What problems is Swagger Studio solving and how is that benefiting you?

Previously, whenever a backend engineer changed how optional fields, null item ages, or pre-tax replacement cost totals were serialized in an API response, it often broke the claims inventory table on our adjuster portal or caused webhook validation errors. Standardizing our contract workflow in Swagger Studio eliminated that drift between backend and frontend teams. When planning a new pricing or settlement endpoint, we draft the OpenAPI 3.1 contract in Swagger Studio first, preview the exact payload schemas in Swagger UI and Elements, and use Diff Mode and Contract Testing to verify that changes remain backward-compatible. Review collected by and hosted on G2.com.