[GH-ISSUE #3135] [bug]: When trying to get graphql schema documentation by connecting it failed. #1033

New issue

Closed

opened 2026-03-16 18:13:14 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @appl4e on GitHub (Jun 13, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3135

Originally assigned to: @anwarulislam on GitHub.

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I try to connect with our graphql api endpoint to fetch the schema documentation then it fails to fetch the schema.

By inspecting, I found that it is not sending the Authorization token I used.
But, when I am clicking on run then it sends a request with my query and gives a successful response. In this case, the bearer token is sent.

In both cases, Authorization Token is set.

Steps to reproduce

Paste the graphql api ur
Set Authorization Token
Click Connect button

Environment

Production

Version

Cloud

Originally created by @appl4e on GitHub (Jun 13, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3135 Originally assigned to: @anwarulislam on GitHub. ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I try to connect with our graphql api endpoint to fetch the schema documentation then it fails to fetch the schema. By inspecting, I found that it is not sending the Authorization token I used. But, when I am clicking on run then it sends a request with my query and gives a successful response. In this case, the bearer token is sent. In both cases, Authorization Token is set. ![image](https://github.com/hoppscotch/hoppscotch/assets/17544501/1845c111-20e3-46d6-811d-cd9a9c6ef399) ### Steps to reproduce 1. Paste the graphql api ur 2. Set Authorization Token 3. Click Connect button ### Environment Production ### Version Cloud

kerem

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

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 18:13:30 +03:00

Author

Owner

@anwarulislam commented on GitHub (Jun 13, 2023):

Thanks for noticing it, brother.
looking into the issue.

@anwarulislam commented on GitHub (Jun 13, 2023): Thanks for noticing it, brother. looking into the issue.

kerem commented

2026-03-16 18:13:35 +03:00

Author

Owner

@NKCSS commented on GitHub (Jun 21, 2023):

Yeah, I have the same issue; the ability to add authentication to the schema/documentation connection would solve this. The thing is, there is no place to input it really, as the auth settings are per request below it, so you'd need a more global setting for the connection.

@NKCSS commented on GitHub (Jun 21, 2023): Yeah, I have the same issue; the ability to add authentication to the schema/documentation connection would solve this. The thing is, there is no place to input it really, as the auth settings are per request below it, so you'd need a more global setting for the connection.

kerem commented

2026-03-16 18:13:40 +03:00

Author

Owner

@liyasthomas commented on GitHub (Jun 27, 2023):

Resolved in #3136, hence closing.

@liyasthomas commented on GitHub (Jun 27, 2023): Resolved in #3136, hence closing.

kerem referenced this issue

2026-03-17 00:40:19 +03:00

[PR #1033] [MERGED] Add trailing backslash to generated cURL code for easier paste-and-execute #3019