starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #4557] [bug]: "Error while importing: format not recognized" when import OpenApi json from URL #1675

New issue

Open

opened 2026-03-16 21:21:30 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 21:21:30 +03:00

Owner

Originally created by @VTrngNghia on GitHub (Nov 25, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4557

Is there an existing issue for this?

I have searched the existing issues

Current behavior

This is not a duplicate of Issue 3796. That issue is about json file, this is about URL.
Workaround: If I download the URL into a JSON file, then HoppScotch imports just fine. It only fails when importing from URL.

My local service generates OpenAPI docs on a local-deployed URL: http://localhost:8183/elastic-searcher/api-docs
Here's what it looks like

{
  "openapi": "3.0.1",
  "info": {
    "title": "Elastic Searcher",
    "version": "1.0"
  },
  "servers": [
    {
      "url": "http://localhost:8183/elastic-searcher",
      "description": "Generated server url"
    }
  ],
...
}

Steps to reproduce

Click on Import/Export
Click on Import from OpenAPI
Click on Import from URL
Use the URL http://localhost:8183/elastic-searcher/api-docs

Environment

Release

Version

Cloud

Originally created by @VTrngNghia on GitHub (Nov 25, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4557 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior 1. This is not a duplicate of [Issue 3796](https://github.com/hoppscotch/hoppscotch/issues/3796). That issue is about json file, this is about URL. 2. Workaround: If I download the URL into a JSON file, then HoppScotch imports just fine. It only fails when importing from URL. My local service generates OpenAPI docs on a local-deployed URL: `http://localhost:8183/elastic-searcher/api-docs` Here's what it looks like ``` { "openapi": "3.0.1", "info": { "title": "Elastic Searcher", "version": "1.0" }, "servers": [ { "url": "http://localhost:8183/elastic-searcher", "description": "Generated server url" } ], ... } ``` ### Steps to reproduce 1. Click on `Import/Export` 2. Click on `Import from OpenAPI` 3. Click on `Import from URL` 4. Use the URL `http://localhost:8183/elastic-searcher/api-docs` ### Environment Release ### Version Cloud

kerem added the

bug

need testing

labels

2026-03-16 21:21:30 +03:00

kerem commented

2026-03-16 21:21:40 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 2, 2024):

We're looking into the issue and will provide updates soon. Thanks for your patience and understanding.

@liyasthomas commented on GitHub (Dec 2, 2024): We're looking into the issue and will provide updates soon. Thanks for your patience and understanding.

kerem commented

2026-03-16 21:21:45 +03:00

Author

Owner

@EmperorArthur commented on GitHub (Feb 24, 2025):

I experienced this same issue. Here are my findings:

Despite the error message, Chrome's console windows shows the request failing because of CORS.

Please update the error message for this case.

This is despite having the website in the browser extension's origins list.

@EmperorArthur commented on GitHub (Feb 24, 2025): I experienced this same issue. Here are my findings: 1. Despite the error message, Chrome's console windows shows the request failing because of CORS. * Please update the error message for this case. 2. This is despite having the website in the browser extension's origins list.

kerem commented

2026-03-16 21:21:51 +03:00

Author

Owner

@yevheniidehtiar commented on GitHub (Mar 19, 2025):

Had the same issue. In my case it was resource that only available behind proxy.
If it has issue by importing from URL - first try to download openapi.json and import it as file.

But I would agree error description is indeed wrong and gives false positive thoughts about the root cause.
Would be nice to explicit error message for cases, when remote url response is not 200 and content-type not application/json or any similar solution.

@yevheniidehtiar commented on GitHub (Mar 19, 2025): Had the same issue. In my case it was resource that only available behind proxy. If it has issue by importing from URL - first try to download openapi.json and import it as file. But I would agree error description is indeed wrong and gives false positive thoughts about the root cause. Would be nice to explicit error message for cases, when remote url response is not 200 and content-type not application/json or any similar solution.

kerem referenced this issue

2026-03-17 01:03:43 +03:00

[PR #1675] [CLOSED] Corrected Hindi Errors in language folder, In file, Now it's perfectly comprehendible. #3448