Feature Request: Support API Key Authentication via Query Parameter (not Header) #14664

Closed
opened 2026-02-21 19:18:14 -05:00 by yindo · 0 comments
Owner

Originally created by @codeMonkey-shin on GitHub (Jun 17, 2025).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Hi team,

When using a custom tool, I need to authenticate by placing the apikey in the query string (e.g., ?apikey=VALUE) rather than in the request header.

Currently, it looks like the authentication options only support sending API keys via headers, and there's no way to specify that the API key should be sent as a query parameter instead.

This is causing integration issues with APIs that require the API key in the query and do not accept it in the header.

Feature request:
Please add support for sending API keys as a query parameter (not just as a header) during authentication for custom tools.

Thank you!

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @codeMonkey-shin on GitHub (Jun 17, 2025). ### Self Checks - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. Hi team, When using a custom tool, I need to authenticate by placing the apikey in the query string (e.g., ?apikey=VALUE) rather than in the request header. Currently, it looks like the authentication options only support sending API keys via headers, and there's no way to specify that the API key should be sent as a query parameter instead. This is causing integration issues with APIs that require the API key in the query and do not accept it in the header. Feature request: Please add support for sending API keys as a query parameter (not just as a header) during authentication for custom tools. Thank you! ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the performanceProposal labels 2026-02-21 19:18:14 -05:00
yindo closed this issue 2026-02-21 19:18:15 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#14664