> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/how-to-import-documents/webhook.md).

# Webhook

借助下方提供的 Webhook API，您只需发送一个简单的 POST 请求，即可轻松将文档直接传输到 DocBits。此 API 旨在简化文件上传到 DocBits 的流程，所有必要参数都已为您填写。

开始使用时，请根据您使用的环境前往以下页面：

PROD: <https://api.docbits.com/docs#/document/process\\_documents\\_document\\_process\\_documents\\_post>

SANDBOX: <https://sandbox.api.docbits.com/docs#/document/process\\_documents\\_document\\_process\\_documents\\_post>

STAGE: <https://stage.api.docbits.com/docs#/document/process\\_documents\\_document\\_process\\_documents\\_post>

使用您的 API 密钥调用 API。您也可以在调用中将要上传的文件作为参数提供。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docbits.com/chinese/zui-zhong-yong-hu-yu-he-zuo-huo-ban/end-user-section/how-to-import-documents/webhook.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.