> 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.md).

# 通过 API 导入

使用 API 手动将主数据发送到 DocBits

主数据通常会通过 ION 数据流自动进入 DocBits。本节中的页面介绍如何通过 API 测试界面手动发送相同的数据——适用于重新导入记录、加载从未成功接收的数据，或在启用自动数据流之前测试新的字段映射。

每个页面都遵循相同的五个步骤：打开适用于你所在环境的 API 链接，使用 Org ID 和 API 密钥进行授权，填写表单，执行操作，并检查数据是否已送达。

* [导入供应商（Supplier BOD）](/chinese/infor-ji-cheng-yu-pei-zhi/importing-customer-master-data/importing-via-the-api/supplier-bod.md)
* [导入采购订单（Purchase Order BOD）](/chinese/infor-ji-cheng-yu-pei-zhi/importing-customer-master-data/importing-via-the-api/purchase-order-bod.md)
* [导入收货记录（Receive Delivery BOD）](/chinese/infor-ji-cheng-yu-pei-zhi/importing-customer-master-data/importing-via-the-api/receive-delivery-bod.md)
* [从 XML 导入主数据](/chinese/infor-ji-cheng-yu-pei-zhi/importing-customer-master-data/importing-via-the-api/master-data-xml.md)

## 所需内容

* **API 密钥** — 请参阅 [API 密钥管理](/chinese/guan-li-yu-she-zhi/settings/global-settings/integration/api-key-management.md)。
* **Org ID** — 位于 **设置 → 集成与 SSO** 下的 **ID** 区域。
* **数据本身**，以 XML 文件形式提供，或提供可粘贴的 XML 内容。

{% hint style="warning" %}
导入会直接写入组织的主数据。执行前，请确认目标环境、区域和组织是否正确。
{% 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.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.