Explore.cli imported Postman consistently getting 400/500 when Export to SwaggerHub
We inherited a legacy API with no swagger docs but fortunately we have a Postman collection. We were able to use explore.cli to import the collection into APIHub Explore with the recent folder changes. However, we are consistently getting 400/500 errors when we try to import the collection from APIHub Explore into SwaggerHub to generate the OpenAPI 3.0. I was able to generate a test Space using History and export those to SwaggerHub. I suspect it maybe due to how the Postman collections are done for our internal ease of use? e.g. We use variables {{host}} and that doesn't seem to translate after import by explore.cli. Here is the snapshot: link. Here's some examples of 400 responses: {"type":"https://problems-registry.smartbear.com/bad-request","title":"Bad Request","detail":"Cannot deserialize value of type `java.lang.String` from Array value (token `JsonToken.START_ARRAY`)\n at [Source: UNKNOWN; byte offset: #UNKNOWN] (through reference chain: io.swagger.v3.oas.models.media.Schema[\"properties\"]->java.util.LinkedHashMap[\"sites\"]->io.swagger.v3.oas.models.media.Schema[\"items\"]->io.swagger.v3.oas.models.media.Schema[\"properties\"]->java.util.LinkedHashMap[\"current_start\"]->io.swagger.v3.oas.models.media.Schema[\"type\"])","status":400} { "timestamp": "2025-02-14T22:22:13.972+00:00", "status": 500, "error": "Internal Server Error", "path": "/spaces-api/v1/exports" }22Views0likes1CommentMass import Postman collection/requests into Swagger Explore API/operation
I inherited an old code base that doesn't have any API documentations and I want to use Swagger Hub for it. We fortunately have a collection in Postman for most of the endpoints. I am following the instructions in the Explore.cli. Explore What's New - Import Postman Collection | SmartBear Community I want to confirm the expected behaviours on import of a Postman collection since this feature is not in the documentations yet: I imported a Postman collection json file of about 60 requests. Each Postman request created an API and within the API contains a singular Operation (e.g. GET /user/). If so, is there a way to import the entire Postman collection's into a single API with the 60 requests as Operations?Solved238Views0likes6CommentsExecute a GraphQL request as HTTP POST in ReadyAPI trial version
I am trying to execute GraphQL requests as an HTTP POST in ReadyAPI trial version and am getting a "400 Bad Request". The requests were imported into ReadyAPI using the ReadyAPI Postman Plugin, and they work just fine in Postman. Why could this be happening? Is there anything specific to ReadyAPI that I am missing? Appreciate any help.571Views0likes1CommentBody request parameters not being created after Swagger definition import
Hi, I'm trying to import a Swagger 2.0 definition to SoapUI, but after doing so the request parameters aren't automatically generating, defeating the purpose of the import. I've also tried to import the example petstore swagger file and even there the body in the post calls is empty even though I can see that there is content when I check the swagger file in the swagger editor. Am I missing something? I have installed the plugins (I believe the latest ones) and I believe the version of the swagger file is correct since it doesn't allow me to import the 3.0. Also I tried importing collections from Postman and in case I have an attribute defined like this: "Expected_Product_Duration": "<hh:mm:ss>" It doesn't import the body request parameters unless we delete the <>. This is not that such of an issue I just thought it would be nice to mention it in case other people encounter the same. Thanks, Bojana PS I found this topic but I don't see how it was resolved, if it was resolved at all: https://community.smartbear.com/t5/SoapUI-Pro/Body-request-parameters-not-being-created-after-Swagger/td-p/152271Solved1.9KViews0likes3CommentsImport Postman Collection
Hello there, We are having issues with the 'Import Postman Collection' functionality in SoapUI Pro. After importing the V1 postman collection with no issues, we get a URISyntaxException when executing any of the imported requests. It sort of looks like the application is not properly doing property expansion when it imports the postman collection. For example if you have 'http://{{host_property}}' defined in your postman request URL, the app does not do a property expansion substitution as stated in the docs: https://www.soapui.org/docs/postman-collections.html. We also tried this in SoapUI community edition and ReadyApi version as well. We suspect the same issue, even though we get a different error message. (e.g.SoapUI community edition gives null pointer exception). Please let us know if there is any work around/solution. thank you.Solved12KViews0likes6Comments