starred/hoppscotch

Fork 0

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

[GH-ISSUE #2259] [feature]: Authorization setting at Collection level #778

New issue

Closed

opened 2026-03-16 17:10:00 +03:00 by kerem · 9 comments

kerem commented

2026-03-16 17:10:00 +03:00

Owner

Originally created by @minhnguyen-ew on GitHub (Apr 13, 2022).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2259

Is there an existing issue for this?

I have searched the existing issues

Summary

In Postman, you can set up an authorization method at the Collection level and all of the requests in that collection will inherit that authorization method (unless you override that in the endpoints themself). We can try to provide a similar mechanism here.

Why should this be worked on?

This is useful for a collection with many different requests (for example, I am working on one which has nearly 100 requests) so you don't need to set up the same authorization method request by request.

Yes, I acknowledged that we can duplicate an endpoint to create another one. But in my case, I imported my collection from Postman. And since I set up the authorization method at the Collection level on Postman, all the requests in the collection don't have one on their own. That means I will need to go and config the authorization method for each request after importing (which is too much work).

Originally created by @minhnguyen-ew on GitHub (Apr 13, 2022). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/2259 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary In Postman, you can set up an authorization method at the Collection level and all of the requests in that collection will inherit that authorization method (unless you override that in the endpoints themself). We can try to provide a similar mechanism here. ### Why should this be worked on? This is useful for a collection with many different requests (for example, I am working on one which has nearly 100 requests) so you don't need to set up the same authorization method request by request. Yes, I acknowledged that we can duplicate an endpoint to create another one. But in my case, I imported my collection from Postman. And since I set up the authorization method at the Collection level on Postman, all the requests in the collection don't have one on their own. That means I will need to go and config the authorization method for each request after importing (which is too much work).

kerem

2026-03-16 17:10:00 +03:00

closed this issue
added the
feature
label

kerem commented

2026-03-16 17:10:16 +03:00

Author

Owner

@stratosgear commented on GitHub (Sep 30, 2022):

Just wanted to add that conceptually, since all API calls in a collection refer to a single API server (otherwise they would not be in that collection) the Authorization method should be common to all of them. No need to duplicate it in all API calls of the collection.

This is one of the most critical missing features that prevents us from adoption of Hoppscotch... :)

@stratosgear commented on GitHub (Sep 30, 2022): Just wanted to add that conceptually, since all API calls in a collection refer to a single API server (otherwise they would not be in that collection) the Authorization method should be common to all of them. No need to duplicate it in all API calls of the collection. This is one of the most critical missing features that prevents us from adoption of Hoppscotch... :)

kerem commented

2026-03-16 17:10:21 +03:00

Author

Owner

@CodeMonkey80s commented on GitHub (Jun 16, 2023):

Any news about this feature? This is really crucial functionality especially for any person with a lots of endpoints defined.

@CodeMonkey80s commented on GitHub (Jun 16, 2023): Any news about this feature? This is really crucial functionality especially for any person with a lots of endpoints defined.

kerem commented

2026-03-16 17:10:26 +03:00

Author

Owner

@stratosgear commented on GitHub (Jun 16, 2023):

We have had great success with the Thunderclient VS Code extension. We really liked Hopscotch but we had to actually choose a tool and that's where we ended up. A nice plus is that all requests/collections are saved withing the project repo so they are always locally available and never lost...

@stratosgear commented on GitHub (Jun 16, 2023): We have had great success with the Thunderclient VS Code extension. We really liked Hopscotch but we had to actually choose a tool and that's where we ended up. A nice plus is that all requests/collections are saved withing the project repo so they are always locally available and never lost...

kerem commented

2026-03-16 17:10:31 +03:00

Author

Owner

@radekpribyl commented on GitHub (Sep 12, 2023):

I'd like to understand the status too - we are also evaluating Hopscotch and this missing feature might be a blocker

@radekpribyl commented on GitHub (Sep 12, 2023): I'd like to understand the status too - we are also evaluating Hopscotch and this missing feature might be a blocker

kerem commented

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

Author

Owner

@liyasthomas commented on GitHub (Sep 12, 2023):

We've prioritized this feature for the next major release, which should happen in December.

@liyasthomas commented on GitHub (Sep 12, 2023): We've prioritized this feature for the next major release, which should happen in December.

kerem commented

2026-03-16 17:10:41 +03:00

Author

Owner

@iam-vatha commented on GitHub (Sep 13, 2023):

We've prioritized this feature for the next major release, which should happen in December.

Thanks.. My team is in the same boat as previous posters. Looking forward to an update as your application is quite good alternative to Postman otherwise.

@iam-vatha commented on GitHub (Sep 13, 2023): > We've prioritized this feature for the next major release, which should happen in December. Thanks.. My team is in the same boat as previous posters. Looking forward to an update as your application is quite good alternative to Postman otherwise.

kerem commented

2026-03-16 17:10:46 +03:00

Author

Owner

@pavelicii commented on GitHub (Sep 26, 2023):

@liyasthomas Will it be possible to also define pre-request script at collection level?

@pavelicii commented on GitHub (Sep 26, 2023): @liyasthomas Will it be possible to also define pre-request script at collection level?

kerem commented

2026-03-16 17:10:51 +03:00

Author

Owner

@bforbis commented on GitHub (Oct 23, 2023):

This seems related to #1741

@bforbis commented on GitHub (Oct 23, 2023): This seems related to #1741

kerem commented

2026-03-16 17:10:56 +03:00

Author

Owner

@liyasthomas commented on GitHub (Dec 20, 2023):

Thanks for your patience and valuable feedback. This feature has been implemented in the latest release.

Closing this ticket as this feature is now available in the recent version. Feel free to reach out if you encounter any further concerns.

Documentation: https://docs.hoppscotch.io/documentation/features/collections#collection-properties

@liyasthomas commented on GitHub (Dec 20, 2023): Thanks for your patience and valuable feedback. This feature has been implemented in the latest release. Closing this ticket as this feature is now available in the recent version. Feel free to reach out if you encounter any further concerns. Documentation: https://docs.hoppscotch.io/documentation/features/collections#collection-properties

kerem referenced this issue

2026-03-17 00:31:22 +03:00

[PR #778] [MERGED] chore(deps-dev): bump start-server-and-test from 1.10.11 to 1.11.0 #2852

kerem referenced this issue

2026-03-17 00:34:21 +03:00

[PR #858] [CLOSED] feat: improve spanish translate #2909