starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #680] [feature]: Public account data #240

New issue

Open

opened 2026-03-16 14:10:36 +03:00 by kerem · 8 comments

kerem commented

2026-03-16 14:10:36 +03:00

Owner

Originally created by @leomp12 on GitHub (Mar 17, 2020).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/680

Is your feature request related to a problem? Please describe.
Imo will be great to be able to share account data, specially collections.
I saw team support planning (https://github.com/liyasthomas/postwoman/issues/580), it will be awesome, but in some cases (at least on mine 😄 ) public collections is the best solution, without login required to read.

Describe the solution you'd like

User may be able to make account data public (read only);
With public account, user will have a custom URL (maybe just a query param) with ID to share;

Describe alternatives you've considered
Teams, but not so good for this case and I think it's even harder to implement.

Additional context
N/A

Originally created by @leomp12 on GitHub (Mar 17, 2020). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/680 **Is your feature request related to a problem? Please describe.** Imo will be great to be able to share account data, specially collections. I saw team support planning (https://github.com/liyasthomas/postwoman/issues/580), it will be awesome, but in some cases (at least on mine :smile: ) public collections is the best solution, without login required to read. **Describe the solution you'd like** - User may be able to make account data public (read only); - With public account, user will have a custom URL (maybe just a query param) with ID to share; **Describe alternatives you've considered** Teams, but not so good for this case and I think it's even harder to implement. **Additional context** N/A

kerem added the

feature

major

labels

2026-03-16 14:10:36 +03:00

kerem commented

2026-03-16 14:10:47 +03:00

Author

Owner

@leomp12 commented on GitHub (Mar 17, 2020):

@liyasthomas I can give a try if you agree and can wait a while again (I'm still kind of busy 😛 )

@leomp12 commented on GitHub (Mar 17, 2020): @liyasthomas I can give a try if you agree and can wait a while again (I'm still kind of busy :stuck_out_tongue: )

kerem commented

2026-03-16 14:10:52 +03:00

Author

Owner

@leomp12 commented on GitHub (Mar 17, 2020):

Additionally, for this purpose will be good to provide URLs for each collection request (another issue?).

@leomp12 commented on GitHub (Mar 17, 2020): Additionally, for this purpose will be good to provide URLs for each collection request (another issue?).

kerem commented

2026-03-16 14:10:57 +03:00

Author

Owner

@liyasthomas commented on GitHub (Mar 17, 2020):

I planned Teams support to be a customizable read-only collections with a sharable ID.

@liyasthomas commented on GitHub (Mar 17, 2020): I planned Teams support to be a customizable read-only collections with a sharable ID.

kerem commented

2026-03-16 14:11:02 +03:00

Author

Owner

@leomp12 commented on GitHub (Mar 18, 2020):

I'm not sure if I understand, will team support work as I described here?
I imagined that the teams would be composed of invited (authenticated) users only, and possibly with write permission, not?

@leomp12 commented on GitHub (Mar 18, 2020): I'm not sure if I understand, will team support work as I described here? I imagined that the teams would be composed of invited (authenticated) users only, and possibly with write permission, not?

kerem commented

2026-03-16 14:11:07 +03:00

Author

Owner

@liyasthomas commented on GitHub (Mar 18, 2020):

I thought of a public/authenticated Collections. Need some refining on it. Will update progress here. Anyways, let this issue stay untill then.

@liyasthomas commented on GitHub (Mar 18, 2020): I thought of a public/authenticated Collections. Need some refining on it. Will update progress here. Anyways, let this issue stay untill then.

kerem commented

2026-03-16 14:11:13 +03:00

Author

Owner

@kondr1 commented on GitHub (Mar 3, 2025):

Is this still in the plans?

@kondr1 commented on GitHub (Mar 3, 2025): Is this still in the plans?

kerem commented

2026-03-16 14:11:18 +03:00

Author

Owner

@liyasthomas commented on GitHub (Mar 3, 2025):

We’re definitely working on making the API documentation and hosting a priority for next quarter. This could be a great starting point for public workspaces and collections.

@liyasthomas commented on GitHub (Mar 3, 2025): We’re definitely working on making the API documentation and hosting a priority for next quarter. This could be a great starting point for public workspaces and collections.

kerem commented

2026-03-16 14:11:23 +03:00

Author

Owner

@MkDev11 commented on GitHub (Feb 25, 2026):

Hi @liyasthomas @jamesgeorge007, I’d like to implement this issue and would appreciate your feedback on this approach before sending a PR.

Scope (MVP)

Share one collection at a time (personal or team) via a read-only link.
User gets a shareable URL (e.g. ?shared=<shareId> or /shared/<shareId>) that works without login.

Backend

New share record (e.g. table or publicShareId on collection) so we can resolve shareId → collection and workspace type.
Unauthenticated read-only endpoint (GraphQL query or REST, similar to existing shortcode / published-docs) that returns the collection tree (reusing current export logic).
Authenticated mutation so only the owner (or team editor/owner) can create/revoke a share.
Throttling on the public endpoint to limit abuse.

Frontend

“Share” / “Get link” in the collection UI (personal and team) that creates a share and copies the URL.
Public view route (e.g. /shared/:shareId) that loads and shows the collection in read-only mode, no login.

Security

Only collection owner (or team with permission) can create/revoke.
Public response limited to that one collection; consider documenting or optionally redacting sensitive auth/env data in the exported payload.

If this direction works for you, I’ll implement accordingly and open a PR. Thanks.

@MkDev11 commented on GitHub (Feb 25, 2026): Hi @liyasthomas @jamesgeorge007, I’d like to implement this issue and would appreciate your feedback on this approach before sending a PR. ### Scope (MVP) - **Share one collection at a time** (personal or team) via a read-only link. - User gets a **shareable URL** (e.g. `?shared=<shareId>` or `/shared/<shareId>`) that works **without login**. ### Backend - New **share record** (e.g. table or `publicShareId` on collection) so we can resolve `shareId` → collection and workspace type. - **Unauthenticated read-only endpoint** (GraphQL query or REST, similar to existing shortcode / published-docs) that returns the collection tree (reusing current export logic). - **Authenticated mutation** so only the owner (or team editor/owner) can create/revoke a share. - **Throttling** on the public endpoint to limit abuse. ### Frontend - **“Share” / “Get link”** in the collection UI (personal and team) that creates a share and copies the URL. - **Public view route** (e.g. `/shared/:shareId`) that loads and shows the collection in **read-only** mode, no login. ### Security - Only collection owner (or team with permission) can create/revoke. - Public response limited to that one collection; consider documenting or optionally redacting sensitive auth/env data in the exported payload. If this direction works for you, I’ll implement accordingly and open a PR. Thanks.

kerem referenced this issue

2026-03-17 00:12:07 +03:00

[PR #240] [MERGED] ⬆️ Bump highlight.js from 9.15.10 to 9.16.2 #2503