[GH-ISSUE #5621] [bug]: Environment values not working in url like (baseURL) when import postman environment file

kerem commented

2026-03-16 23:28:08 +03:00

Owner

Originally created by @FaisalFaraj on GitHub (Nov 27, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5621

Originally assigned to: @FaisalFaraj 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

Here’s an updated issue text you can paste and tweak:

What happened?

When importing a Postman environment file into Hoppscotch and using it in requests, the app does not correctly resolve environment variables in the request path. The variable placeholder <<baseUrl>> stays highlighted in purple in the URL bar instead of being replaced with the actual value, and every request returns a 405 status code even though the backend is running correctly.[11][12]

Steps to reproduce

Open the web version at https://hoppscotch.io/.
Import a Postman environment JSON file that defines a baseUrl variable with value http://localhost:8089.
Select the imported environment.
Create or open a request whose URL uses the variable in the path, for example <<baseUrl>>/api/....
Send the request.
Observe that:
- The URL field still shows <<baseUrl>>/api/... in purple instead of resolving to http://localhost:8089/api/....
- The response status is always 405.

What I expected

Hoppscotch should replace <<baseUrl>> with http://localhost:8089 in the request URL when the environment is active.
The request should be sent to the correct endpoint and return the same successful response that is obtained when running the equivalent curl command directly in the terminal.

Screenshots

Screenshots attached showing the unresolved <<baseUrl>> in the URL bar and the environment configuration.[12][11]

Additional context

In previous versions of Hoppscotch this exact setup worked perfectly; the same Postman environment import and requests resolved the variables correctly and the API calls succeeded.
When using “Generate curl” for the same request, the generated curl command contains the correct expanded URL (http://localhost:8089/...), and running that curl command in the terminal works as expected, returning a successful response.
This suggests the environment value is loaded correctly for curl generation but not applied when actually sending the request from the web UI.
Backend: local server on http://localhost:8089 that responds correctly to the same endpoint when called via curl.

Deployment Type

Hoppscotch Cloud

Version

2025.10.1

Originally created by @FaisalFaraj on GitHub (Nov 27, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5621 Originally assigned to: @FaisalFaraj 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 Here’s an updated issue text you can paste and tweak: *** ## What happened? When importing a Postman environment file into Hoppscotch and using it in requests, the app does not correctly resolve environment variables in the request path. The variable placeholder `<<baseUrl>>` stays highlighted in purple in the URL bar instead of being replaced with the actual value, and every request returns a 405 status code even though the backend is running correctly.[11][12] ## Steps to reproduce 1. Open the web version at https://hoppscotch.io/. 2. Import a Postman environment JSON file that defines a `baseUrl` variable with value `http://localhost:8089`. 3. Select the imported environment. 4. Create or open a request whose URL uses the variable in the path, for example `<<baseUrl>>/api/...`. 5. Send the request. 6. Observe that: - The URL field still shows `<<baseUrl>>/api/...` in purple instead of resolving to `http://localhost:8089/api/...`. - The response status is always 405. ## What I expected - Hoppscotch should replace `<<baseUrl>>` with `http://localhost:8089` in the request URL when the environment is active. - The request should be sent to the correct endpoint and return the same successful response that is obtained when running the equivalent curl command directly in the terminal. ## Screenshots Screenshots attached showing the unresolved `<<baseUrl>>` in the URL bar and the environment configuration.[12][11] ## Additional context - In previous versions of Hoppscotch this exact setup worked perfectly; the same Postman environment import and requests resolved the variables correctly and the API calls succeeded. - When using “Generate curl” for the same request, the generated curl command contains the correct expanded URL (`http://localhost:8089/...`), and running that curl command in the terminal works as expected, returning a successful response. - This suggests the environment value is loaded correctly for curl generation but not applied when actually sending the request from the web UI. - Backend: local server on `http://localhost:8089` that responds correctly to the same endpoint when called via curl. <img width="1363" height="766" alt="Image" src="https://github.com/user-attachments/assets/7000db38-d6dc-4da4-bcf4-4fbe921f0370" /> <img width="1440" height="766" alt="Image" src="https://github.com/user-attachments/assets/4a846fa1-3e8e-4a9c-901d-5985daa69e26" /> <img width="1440" height="766" alt="Image" src="https://github.com/user-attachments/assets/686b30c4-bc89-4b26-9a2c-d95b6a3347c5" /> <img width="1440" height="766" alt="Image" src="https://github.com/user-attachments/assets/a1f96c93-437e-46d8-9a15-01c22db30cb8" /> ### Deployment Type Hoppscotch Cloud ### Version 2025.10.1

kerem added the

bug

need testing

labels

2026-03-16 23:28:08 +03:00

kerem commented

2026-03-16 23:28:19 +03:00

Author

Owner

@FaisalFaraj commented on GitHub (Nov 27, 2025):

Hey, thanks for the awesome app, I use Hoppscotch a lot.
I’ve reproduced this bug on the web version and I’d like to work on a fix, so assign this issue to me, could you?

@FaisalFaraj commented on GitHub (Nov 27, 2025): Hey, thanks for the awesome app, I use Hoppscotch a lot. I’ve reproduced this bug on the web version and I’d like to work on a fix, so assign this issue to me, could you?

kerem commented

2026-03-16 23:28:24 +03:00

Author

Owner

@FaisalFaraj commented on GitHub (Nov 27, 2025):

@CuriousCorrelation

@FaisalFaraj commented on GitHub (Nov 27, 2025): @CuriousCorrelation

kerem commented

2026-03-16 23:28:29 +03:00

Author

Owner

@nivedin commented on GitHub (Dec 5, 2025):

@FaisalFaraj can you check if the mentioned variable is defined in any of the parent collections of the request as a collection variable? The highlighted environment variable indicates that an empty collection variable is currently active.

@nivedin commented on GitHub (Dec 5, 2025): @FaisalFaraj can you check if the mentioned variable is defined in any of the parent collections of the request as a collection variable? The highlighted environment variable indicates that an empty collection variable is currently active.

kerem commented

2026-03-16 23:28:34 +03:00

Author

Owner

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

@FaisalFaraj can you check if the mentioned variable is defined in any of the parent collections of the request as a collection variable? The highlighted environment variable indicates that an empty collection variable is currently active.

I think I have a similar issue when import from Postman, I sent a new reply here: https://github.com/hoppscotch/hoppscotch/issues/5583 ^^

@AaronFortG commented on GitHub (Dec 5, 2025): > [@FaisalFaraj](https://github.com/FaisalFaraj) can you check if the mentioned variable is defined in any of the parent collections of the request as a collection variable? The highlighted environment variable indicates that an empty collection variable is currently active. I think I have a similar issue when import from Postman, I sent a new reply here: https://github.com/hoppscotch/hoppscotch/issues/5583 ^^

kerem commented

2026-03-16 23:28:39 +03:00

Author

Owner

@FaisalFaraj commented on GitHub (Dec 9, 2025):

Yes, I have checked the parent collections, and I confirmed that the
variable is not defined there. The issue persists even after verifying that
there are no empty collection variables shadowing the environment variable.

On Fri, Dec 5, 2025 at 3:54 PM Nivedin @.***> wrote:

nivedin left a comment (hoppscotch/hoppscotch#5621)
https://github.com/hoppscotch/hoppscotch/issues/5621#issuecomment-3617023886

@FaisalFaraj https://github.com/FaisalFaraj can you check if the
mentioned variable is defined in any of the parent collections of the
request as a collection variable? The highlighted environment variable
indicates that an empty collection variable is currently active.

—
Reply to this email directly, view it on GitHub
https://github.com/hoppscotch/hoppscotch/issues/5621#issuecomment-3617023886,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR2BGDLDHKZ4TE77NSKBI434AGFC7AVCNFSM6AAAAACNKBFRPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMJXGAZDGOBYGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@FaisalFaraj commented on GitHub (Dec 9, 2025): Yes, I have checked the parent collections, and I confirmed that the variable is not defined there. The issue persists even after verifying that there are no empty collection variables shadowing the environment variable. On Fri, Dec 5, 2025 at 3:54 PM Nivedin ***@***.***> wrote: > *nivedin* left a comment (hoppscotch/hoppscotch#5621) > <https://github.com/hoppscotch/hoppscotch/issues/5621#issuecomment-3617023886> > > @FaisalFaraj <https://github.com/FaisalFaraj> can you check if the > mentioned variable is defined in any of the parent collections of the > request as a collection variable? The highlighted environment variable > indicates that an empty collection variable is currently active. > > — > Reply to this email directly, view it on GitHub > <https://github.com/hoppscotch/hoppscotch/issues/5621#issuecomment-3617023886>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AR2BGDLDHKZ4TE77NSKBI434AGFC7AVCNFSM6AAAAACNKBFRPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMJXGAZDGOBYGY> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

kerem commented

2026-03-16 23:28:44 +03:00

Author

Owner

@FaisalFaraj commented on GitHub (Dec 9, 2025):

Yes, I have checked the parent collections, and I confirmed that the
variable is not defined there. The issue persists even after verifying that
there are no empty collection variables shadowing the environment variable.

On Fri, Dec 5, 2025 at 5:46 PM Aaron Fort Garcia @.***>
wrote:

AaronFortG left a comment (hoppscotch/hoppscotch#5621)
https://github.com/hoppscotch/hoppscotch/issues/5621#issuecomment-3617442054

@FaisalFaraj https://github.com/FaisalFaraj can you check if the
mentioned variable is defined in any of the parent collections of the
request as a collection variable? The highlighted environment variable
indicates that an empty collection variable is currently active.

I think I have a similar issue when import from Postman, I sent a new
reply here: #5583 https://github.com/hoppscotch/hoppscotch/issues/5583
^^

—
Reply to this email directly, view it on GitHub
https://github.com/hoppscotch/hoppscotch/issues/5621#issuecomment-3617442054,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR2BGDOBPKZFTFJA5O2IBDT4AGSDTAVCNFSM6AAAAACNKBFRPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMJXGQ2DEMBVGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@FaisalFaraj commented on GitHub (Dec 9, 2025): Yes, I have checked the parent collections, and I confirmed that the variable is not defined there. The issue persists even after verifying that there are no empty collection variables shadowing the environment variable. On Fri, Dec 5, 2025 at 5:46 PM Aaron Fort Garcia ***@***.***> wrote: > *AaronFortG* left a comment (hoppscotch/hoppscotch#5621) > <https://github.com/hoppscotch/hoppscotch/issues/5621#issuecomment-3617442054> > > @FaisalFaraj <https://github.com/FaisalFaraj> can you check if the > mentioned variable is defined in any of the parent collections of the > request as a collection variable? The highlighted environment variable > indicates that an empty collection variable is currently active. > > I think I have a similar issue when import from Postman, I sent a new > reply here: #5583 <https://github.com/hoppscotch/hoppscotch/issues/5583> > ^^ > > — > Reply to this email directly, view it on GitHub > <https://github.com/hoppscotch/hoppscotch/issues/5621#issuecomment-3617442054>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AR2BGDOBPKZFTFJA5O2IBDT4AGSDTAVCNFSM6AAAAACNKBFRPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMJXGQ2DEMBVGQ> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

kerem commented

2026-03-16 23:28:49 +03:00

Author

Owner

@nivedin commented on GitHub (Jan 22, 2026):

@FaisalFaraj can you check if you are still able to reproduce the issue anymore in the latest app version.

@nivedin commented on GitHub (Jan 22, 2026): @FaisalFaraj can you check if you are still able to reproduce the issue anymore in the latest app version.

kerem commented

2026-03-16 23:28:55 +03:00

Author

Owner

@Saket-Entujn commented on GitHub (Feb 19, 2026):

I'm using the Hoppscotch desktop application and I'm facing the same issue where the <> is not fetching the value from the variable which is defined in the environment. I've checked the value for the variable in environment it does not contain any empty spaces. I'd kindly like to know this issue has any known solutions.

@Saket-Entujn commented on GitHub (Feb 19, 2026): I'm using the Hoppscotch desktop application and I'm facing the same issue where the <<baseUrl>> is not fetching the value from the variable which is defined in the environment. I've checked the value for the variable in environment it does not contain any empty spaces. I'd kindly like to know this issue has any known solutions.

kerem commented

2026-03-16 23:29:00 +03:00

Author

Owner

@nivedin commented on GitHub (Feb 19, 2026):

I'm using the Hoppscotch desktop application and I'm facing the same issue where the <> is not fetching the value from the variable which is defined in the environment. I've checked the value for the variable in environment it does not contain any empty spaces. I'd kindly like to know this issue has any known solutions.

In Hoppscotch we use <<variable-name>> format to use environment variables, can you try that out.
You can follow our doc for more info on environments and its usage.

@nivedin commented on GitHub (Feb 19, 2026): > I'm using the Hoppscotch desktop application and I'm facing the same issue where the <> is not fetching the value from the variable which is defined in the environment. I've checked the value for the variable in environment it does not contain any empty spaces. I'd kindly like to know this issue has any known solutions. In Hoppscotch we use `<<variable-name>>` format to use environment variables, can you try that out. You can follow our [doc](https://docs.hoppscotch.io/documentation/features/environments#creating-an-environment) for more info on environments and its usage.

kerem commented

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

Author

Owner

@Saket-Entujn commented on GitHub (Feb 19, 2026):

@nivedin Thanks for the reply in my environment I'm using **<< baseUrl >>**and using the same variable in my collections but one collection namely the last collection it is not fetching the value for the variable from the environment even though rest of collections are getting the value.

@Saket-Entujn commented on GitHub (Feb 19, 2026): @nivedin Thanks for the reply in my environment I'm using **<< baseUrl >>**and using the same variable in my collections but one collection namely the last collection it is not fetching the value for the variable from the environment even though rest of collections are getting the value.

kerem commented

2026-03-16 23:29:10 +03:00

Author

Owner

@nivedin commented on GitHub (Feb 20, 2026):

@nivedin Thanks for the reply in my environment I'm using **<< baseUrl >>**and using the same variable in my collections but one collection namely the last collection it is not fetching the value for the variable from the environment even though rest of collections are getting the value.

@Saket-Entujn If possible can you share your collections where this issue exists, so we can debug this

@nivedin commented on GitHub (Feb 20, 2026): > [@nivedin](https://github.com/nivedin) Thanks for the reply in my environment I'm using **<< baseUrl >>**and using the same variable in my collections but one collection namely the last collection it is not fetching the value for the variable from the environment even though rest of collections are getting the value. @Saket-Entujn If possible can you share your collections where this issue exists, so we can debug this

kerem referenced this issue

2026-03-17 01:15:13 +03:00

[PR #2175] [MERGED] Supporting Raw Body Imports from Postman #3657

Rows
Columns

[GH-ISSUE #5621] [bug]: Environment values not working in url like (baseURL) when import postman environment file #2175

Is there an existing issue for this?

Platform

Browser

Operating System

Bug Description

What happened?

Steps to reproduce

What I expected

Screenshots

Additional context

Deployment Type

Version