> 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/infor-ji-cheng-yu-pei-zhi/importing-customer-master-data/importing-via-the-api/supplier-bod.md).
# 导入供应商（Supplier BOD）
如何使用 API 手动将 Supplier BOD 导入 DocBits
供应商主数据通常会通过 ION 数据流自动传入 DocBits。本页介绍如何手动发送 **Supplier BOD**，适用于重新导入供应商、导入未成功送达的一批数据，或在启用自动数据流之前测试字段映射。
## 通过两种方式发送同一个 BOD
有两个端点，功能相同。唯一的区别是提交 BOD 的方式：
Supplier BOD 会在您等待期间完成处理，因此看到此消息时，数据已经导入。
如果请求有误，响应会包含 `"success": false`，并附上一条说明问题的消息。最常见的原因包括：内容不是供应商 BOD，或者您的 API 密钥无权访问该 Org ID。
### 5. 检查数据是否已导入
* 在 DocBits 中，前往 **设置 → 文档处理 → 查找主数据**。
* 在左侧选择 **BOD Input Data**，然后打开 **Supplier** 选项卡。
* 搜索 BOD 中的供应商。
{% hint style="info" %}
DocBits 会根据 BOD 内部的类型来决定如何处理，而不是根据您使用的导入端点来判断。如果您误将采购订单 BOD 发送到此处，它会作为采购订单导入，而不会被拒绝。因此，请确认数据出现在预期的选项卡中。
{% endhint %}
---
# 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/infor-ji-cheng-yu-pei-zhi/importing-customer-master-data/importing-via-the-api/supplier-bod.md?ask=&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.
