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

Using a Custom Tool for an API with Bearer Token returns 400 Bad Request #5343

New Issue
Closed
opened 2026-02-21 18:10:30 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:10:30 -05:00
Owner
Copy Link
Copy Source

Originally created by @Banbury on GitHub (Sep 2, 2024).

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

0.7.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  • Create a custom tool for an API that uses a Bearer Token.
  • Create an API token for the other application
  • Press 'Test' for one of the endpoints and use the token as a bearer token

I have attached the OpenAPI spec for Home Assistant. But unless you have an installation of HA, it won't help much.
ha.json
I have successfully used other unprotected APIs on the same network.

✔️ Expected Behavior

I would expect the test to succeed. I have tried the endpoint with curl and the same token on the same machine and it works.

❌ Actual Behavior

I get the message Request failed with status code 400 and 400: Bad Request.
The log file contains the line 2024-09-02 10:33:25 api-1 | 2024-09-02 08:33:25,743.743 INFO [Dummy-2] [_client.py:1026] - HTTP Request: GET http://192.168.1.115:8123/api/ "HTTP/1.1 400 Bad Request"
I have tried to increase the log level, but your code doesn't seem to contain any Debug level log messages.
I can only assume, that the HTTP request is malformed on your side.

Originally created by @Banbury on GitHub (Sep 2, 2024). ### 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 0.7.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce * Create a custom tool for an API that uses a Bearer Token. * Create an API token for the other application * Press 'Test' for one of the endpoints and use the token as a bearer token I have attached the OpenAPI spec for Home Assistant. But unless you have an installation of HA, it won't help much. [ha.json](https://github.com/user-attachments/files/16834858/ha.json) I have successfully used other unprotected APIs on the same network. ### ✔️ Expected Behavior I would expect the test to succeed. I have tried the endpoint with curl and the same token on the same machine and it works. ### ❌ Actual Behavior I get the message `Request failed with status code 400 and 400: Bad Request`. The log file contains the line `2024-09-02 10:33:25 api-1 | 2024-09-02 08:33:25,743.743 INFO [Dummy-2] [_client.py:1026] - HTTP Request: GET http://192.168.1.115:8123/api/ "HTTP/1.1 400 Bad Request"` I have tried to increase the log level, but your code doesn't seem to contain any Debug level log messages. I can only assume, that the HTTP request is malformed on your side.
yindo added the 🐞 bug label 2026-02-21 18:10:30 -05:00
yindo closed this issue 2026-02-21 18:10:30 -05:00
yindo commented 2026-02-21 18:10:30 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 2, 2024):

I found a similar closed issue that might be relevant to your problem: Custom tool with API Key. The suggested solution was to change the endpoint to use HTTP instead of HTTPS due to a self-signed certificate issue.

For your specific issue with the Bearer Token returning a 400 Bad Request in Dify version 0.7.2, while the same token works with curl, it could be due to the specific structure and requirements of the API request as defined by Dify.

Here are the key points to check:

  1. Headers:

    • Content-Type should be application/json.
    • Authorization should be in the format Bearer {api_key}.

  2. Request Body:

    • The body should be a JSON object containing a point and params.

Here is an example of how the request should be structured:

{
    "point": "app.external_data_tool.query",
    "params": {
        "app_id": "61248ab4-1125-45be-ae32-0ce91334d021",
        "tool_variable": "weather_retrieve",
        "inputs": {
            "location": "London"
        },
        "query": "How's the weather today?"
    }
}

Ensure that your custom tool sends the request in this format and includes the correct headers. This should resolve the 400 Bad Request error [1][2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Sep 2, 2024): <!-- Answer --> I found a similar closed issue that might be relevant to your problem: [Custom tool with API Key](https://github.com/langgenius/dify/issues/7412). The suggested solution was to change the endpoint to use HTTP instead of HTTPS due to a self-signed certificate issue. For your specific issue with the Bearer Token returning a 400 Bad Request in Dify version 0.7.2, while the same token works with curl, it could be due to the specific structure and requirements of the API request as defined by Dify. Here are the key points to check: 1. **Headers**: - `Content-Type` should be `application/json`. - `Authorization` should be in the format `Bearer {api_key}`. 2. **Request Body**: - The body should be a JSON object containing a `point` and `params`. Here is an example of how the request should be structured: ```json { "point": "app.external_data_tool.query", "params": { "app_id": "61248ab4-1125-45be-ae32-0ce91334d021", "tool_variable": "weather_retrieve", "inputs": { "location": "London" }, "query": "How's the weather today?" } } ``` Ensure that your custom tool sends the request in this format and includes the correct headers. This should resolve the 400 Bad Request error <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/extension/api_based_extension/README.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/extension/api-based-extension/README.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:10:30 -05:00
Author
Owner
Copy Link
Copy Source

@Banbury commented on GitHub (Sep 2, 2024):

After restarting the HA server the error went away. Go figure.

@Banbury commented on GitHub (Sep 2, 2024): After restarting the HA server the error went away. Go figure.
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 🐞 bug
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#5343
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?