langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 03:55:25 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

The Apps support API-Key search #16044

New Issue
Closed
opened 2026-02-21 19:24:27 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:24:27 -05:00
Owner
Copy Link
Copy Source

Originally created by @xw2723 on GitHub (Aug 11, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 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.

1. Feature Request/User Story

As a developer, I want to quickly locate Dify applications by API-Key without relying on ad hoc code annotations.

2. Problem Statement

As more and more Dify applications are deployed across multiple systems, the only reliable identifier in the logs is the API-Key.
Currently:
The Apps list only supports filtering by name, tag, or creation time.
There is no way to search by the actual API-Key string.
Developers must maintain manual annotations in the source code to trace back to the correct application, which is error-prone and impossible to enforce.

3. Proposed Solution

Add a new search filter to the Apps page (/Apps) that accepts either an API-Key prefix or the full key and returns matching applications.

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 @xw2723 on GitHub (Aug 11, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [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. #### 1. Feature Request/User Story As a developer, I want to quickly locate Dify applications by API-Key without relying on ad hoc code annotations. #### 2. Problem Statement As more and more Dify applications are deployed across multiple systems, the only reliable identifier in the logs is the API-Key. Currently: The Apps list only supports filtering by name, tag, or creation time. There is no way to search by the actual API-Key string. Developers must maintain manual annotations in the source code to trace back to the correct application, which is error-prone and impossible to enforce. #### 3. Proposed Solution Add a new search filter to the Apps page (/Apps) that accepts either an API-Key prefix or the full key and returns matching applications. ### 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 💪 enhancementfeat:webapp labels 2026-02-21 19:24:27 -05:00
yindo closed this issue 2026-02-21 19:24:27 -05:00
yindo commented 2026-02-21 19:24:27 -05:00
Author
Owner
Copy Link
Copy Source

@ZombieBlue commented on GitHub (Aug 11, 2025):

I will help to do this.

@ZombieBlue commented on GitHub (Aug 11, 2025): I will help to do this.
yindo commented 2026-02-21 19:24:27 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 12, 2025):

Hi, @xw2723. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary

  • You requested an API-Key search filter on the Apps page to improve app traceability.
  • Maintainer ZombieBlue volunteered to implement this feature.
  • You provided positive feedback on the proposed implementation.
  • The issue is currently unresolved and no recent updates have been made.

Next Steps

  • Please let me know if this feature is still relevant to the latest version of Dify by commenting on this issue.
  • If I do not hear back within 15 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 12, 2025): Hi, @xw2723. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary** - You requested an API-Key search filter on the Apps page to improve app traceability. - Maintainer ZombieBlue volunteered to implement this feature. - You provided positive feedback on the proposed implementation. - The issue is currently unresolved and no recent updates have been made. **Next Steps** - Please let me know if this feature is still relevant to the latest version of Dify by commenting on this issue. - If I do not hear back within 15 days, I will automatically close this issue. Thank you for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label feat:webapp 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#16044
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?