[GH-ISSUE #4968] [feature]: Re-import OpenAPI Spec from URL #1883

Open
opened 2026-03-16 22:15:00 +03:00 by kerem · 0 comments
Owner

Originally created by @jkronlachner on GitHub (Apr 8, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4968

Is there an existing issue for this?

  • I have searched the existing issues

Summary

This feature would enable Hoppscotch users to automatically re-import their OpenAPI specification from a URL (e.g., an OpenAPI JSON or YAML file hosted on a server). This will ensure that users can work with the most up-to-date version of their API schema directly within Hoppscotch, without having to manually update the API collection each time their backend changes.

Why should this be worked on?

When developing APIs, backend changes often occur, resulting in modifications to the OpenAPI specification. Currently, users need to manually re-import the updated OpenAPI spec into Hoppscotch, which is time-consuming, error-prone and values get lost.

This feature would streamline the development workflow by automating the re-import process, ensuring that any new or modified endpoints are instantly reflected in the Hoppscotch folder. This would be especially beneficial for teams working on rapidly changing APIs, as it ensures they always work with the latest version of the API specification.

Originally created by @jkronlachner on GitHub (Apr 8, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4968 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary This feature would enable Hoppscotch users to automatically re-import their OpenAPI specification from a URL (e.g., an OpenAPI JSON or YAML file hosted on a server). This will ensure that users can work with the most up-to-date version of their API schema directly within Hoppscotch, without having to manually update the API collection each time their backend changes. ### Why should this be worked on? When developing APIs, backend changes often occur, resulting in modifications to the OpenAPI specification. Currently, users need to manually re-import the updated OpenAPI spec into Hoppscotch, which is time-consuming, error-prone and values get lost. This feature would streamline the development workflow by automating the re-import process, ensuring that any new or modified endpoints are instantly reflected in the Hoppscotch folder. This would be especially beneficial for teams working on rapidly changing APIs, as it ensures they always work with the latest version of the API specification.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#1883
No description provided.