mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4968] [feature]: Re-import OpenAPI Spec from URL #1883
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1883
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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?
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.