langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

Registering Perplexity Plugin with API key leads to 400 bad request error #430

New Issue
Closed
opened 2026-02-16 10:19:24 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:19:24 -05:00
Owner
Copy Link
Copy Source

Originally created by @dev-redempto-lr on GitHub (Jul 8, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

1.4.0 and 1.5.1

Cloud or Self Hosted

Self Hosted (Docker), Cloud

Steps to reproduce

Issue

I'm not sure if this has been brought up before, but I am unable to register Perplexity as a plugin. Whenever I input my API key for Perplexity (starting at pplx-xxxx...), it returns an error saying it's a bad request. Here are the environments I tested this on

  • Dify Self-Hosted
    • 1.4.0
  • Dify Cloud
    • 1.5.1

✔️ Expected Behavior

Inputting API key in Perplexity Plugin Setup should be a success

❌ Actual Behavior

Image
Originally created by @dev-redempto-lr on GitHub (Jul 8, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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. ### Dify version 1.4.0 and 1.5.1 ### Cloud or Self Hosted Self Hosted (Docker), Cloud ### Steps to reproduce # Issue I'm not sure if this has been brought up before, but I am unable to register Perplexity as a plugin. Whenever I input my API key for Perplexity (starting at `pplx-xxxx...`), it returns an error saying it's a bad request. Here are the environments I tested this on - Dify Self-Hosted - 1.4.0 - Dify Cloud - 1.5.1 ### ✔️ Expected Behavior Inputting API key in Perplexity Plugin Setup should be a success ### ❌ Actual Behavior <img width="428" height="371" alt="Image" src="https://github.com/user-attachments/assets/f5435d8d-3bb3-4e56-b30c-55de8ab98b9c" />
yindo closed this issue 2026-02-16 10:19:24 -05:00
yindo commented 2026-02-16 10:19:24 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 8, 2025):

Hi @dev-redempto-lr! I'm Dosu and I’m helping the dify team.

Perplexity is not currently supported as a plugin provider in Dify. There is no integration or credential schema for Perplexity in the codebase, so attempts to register it will always fail with a 400 Bad Request error due to missing validation logic. This is consistent across both self-hosted and cloud versions you mentioned.

There is a related issue with the Perplexity API and 400 errors when using certain parameters, but even with correct parameters, Dify does not have the necessary support to register Perplexity as a provider at this time see details.

If you need Perplexity support, you may want to monitor for future updates or request it as a feature. For now, there is no workaround to register Perplexity as a plugin in Dify.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 8, 2025): <!-- Greeting --> Hi @dev-redempto-lr! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> Perplexity is not currently supported as a plugin provider in Dify. There is no integration or credential schema for Perplexity in the codebase, so attempts to register it will always fail with a 400 Bad Request error due to missing validation logic. This is consistent across both self-hosted and cloud versions you mentioned. There is a related issue with the Perplexity API and 400 errors when using certain parameters, but even with correct parameters, Dify does not have the necessary support to register Perplexity as a provider at this time [see details](https://github.com/langgenius/dify/issues/17080). If you need Perplexity support, you may want to monitor for future updates or request it as a feature. For now, there is no workaround to register Perplexity as a plugin in Dify. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/cccc9867-9747-4422-930a-39ef1f943c17?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/cccc9867-9747-4422-930a-39ef1f943c17?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/cccc9867-9747-4422-930a-39ef1f943c17?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/cccc9867-9747-4422-930a-39ef1f943c17?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/cccc9867-9747-4422-930a-39ef1f943c17?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/cccc9867-9747-4422-930a-39ef1f943c17?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/cccc9867-9747-4422-930a-39ef1f943c17?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/22044)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
No Label
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-official-plugins#430
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?