starred/hoppscotch

Fork 0

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

[GH-ISSUE #5688] [bug]: Collection Authorization method passed as Query Parameter by default #2210

New issue

Closed

opened 2026-03-16 23:35:05 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 23:35:05 +03:00

Owner

Originally created by @AaronFortG on GitHub (Dec 11, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5688

Originally assigned to: @anwarulislam, @AaronFortG on GitHub.

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Platform

Web App

Browser

Chrome

Operating System

macOS

Bug Description

What happened?

When exporting a Collection from Postman, which has the Authorization method set as API Key added to the Header, and importing it to Hoppscotch, the Authorization method is passed as Query Parameter (instead if Header as originally was set).

How to reproduce?

Export Collection from Postman using JSON with v2.1
Import Collection into Hoppscotch
Check how Authorization is passed into requests (inside Collection's properties).

Screenshots

Postman Authorization method:

Hoppscotch Authorization method:

More context

From what I see, when exporting the Collection from Postman as JSON there are these two different dumps:

When Authorization is set as Query Parameter in Postman:

    "auth": {
		"type": "apikey",
		"apikey": [
			{
				"key": "in",
				"value": "query",
				"type": "string"
			},
			{
				"key": "value",
				"value": "{{AUTH_TOKEN}}",
				"type": "string"
			},
			{
				"key": "key",
				"value": "Authorization",
				"type": "string"
			}
		]
	},

When Authorization is set as Header in Postman:

    "auth": {
		"type": "apikey",
		"apikey": [
			{
				"key": "value",
				"value": "{{AUTH_TOKEN}}",
				"type": "string"
			},
			{
				"key": "key",
				"value": "Authorization",
				"type": "string"
			}
		]
	},

As we can see, the key "in" only appears when it's a Query Parameter, so that could be useful when trying to fix this issue and determine wether the collection imported uses Header or Query Parameters for the Authorization method, in order to avoid setting an invalid initial value.

Deployment Type

Hoppscotch Cloud

Version

latest (since using hoppscotch.io web)

Originally created by @AaronFortG on GitHub (Dec 11, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5688 Originally assigned to: @anwarulislam, @AaronFortG on GitHub. ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Platform Web App ### Browser Chrome ### Operating System macOS ### Bug Description ## What happened? When exporting a Collection from Postman, which has the Authorization method set as API Key added to the **Header**, and importing it to Hoppscotch, the Authorization method is passed as **Query Parameter** (instead if Header as originally was set). ## How to reproduce? 1. Export Collection from Postman using JSON with v2.1 2. Import Collection into Hoppscotch 3. Check how Authorization is passed into requests (inside Collection's properties). ## Screenshots ### Postman Authorization method: <img width="791" height="478" alt="Image" src="https://github.com/user-attachments/assets/6326a8b2-2596-4093-aa39-c02e1a26f133" /> ### Hoppscotch Authorization method: <img width="1013" height="320" alt="Image" src="https://github.com/user-attachments/assets/9d806577-9d29-4814-a48f-6816334c3dd5" /> ## More context From what I see, when exporting the Collection from Postman as JSON there are these two different dumps: When Authorization is set as **Query Parameter** in Postman: ```json "auth": { "type": "apikey", "apikey": [ { "key": "in", "value": "query", "type": "string" }, { "key": "value", "value": "{{AUTH_TOKEN}}", "type": "string" }, { "key": "key", "value": "Authorization", "type": "string" } ] }, ``` When Authorization is set as **Header** in Postman: ```json "auth": { "type": "apikey", "apikey": [ { "key": "value", "value": "{{AUTH_TOKEN}}", "type": "string" }, { "key": "key", "value": "Authorization", "type": "string" } ] }, ``` As we can see, the key "in" only appears when it's a Query Parameter, so that could be useful when trying to fix this issue and determine wether the collection imported uses Header or Query Parameters for the Authorization method, in order to avoid setting an invalid initial value. ### Deployment Type Hoppscotch Cloud ### Version latest (since using hoppscotch.io web)

kerem

2026-03-16 23:35:05 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-16 23:35:21 +03:00

Author

Owner

@AaronFortG commented on GitHub (Dec 16, 2025):

I just did a PR fixing this issue (#5701), feel free to check it out and let me know guys @jamesgeorge007 @anwarulislam 😉

@AaronFortG commented on GitHub (Dec 16, 2025): I just did a PR fixing this issue (#5701), feel free to check it out and let me know guys @jamesgeorge007 @anwarulislam 😉

kerem commented

2026-03-16 23:35:26 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Dec 22, 2025):

This is now addressed in the v2025.12.0 release.

@jamesgeorge007 commented on GitHub (Dec 22, 2025): This is now addressed in the [v2025.12.0](https://github.com/hoppscotch/hoppscotch/releases/tag/2025.12.0) release.

kerem referenced this issue

2026-03-17 01:16:02 +03:00

[PR #2210] [MERGED] feat: remember last selected team id #3673