> 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/exporting-to-infor/creating-an-ion-api-endpoint.md).

# 为 DocBits 导出创建 Infor ION API 端点

Infor 管理员会为**特定的 DocBits 环境和组织**配置 API Gateway 端点。本页的旧截图展示的是一个历史 Infor 租户、固定的 `api.docbits.com` 示例和旧版 DocBits Export 表单。请使用适用于实际环境的已批准目标 URL、API 密钥和 OpenAPI 文档。本次更新未连接任何 Infor 租户，也未保存端点。

## 开始之前

请向集成管理员获取目标 DocBits API URL、已批准的 API 密钥及其请求头名称、OpenAPI URL，以及计划使用的 Infor 和 DocBits 环境。请勿将密钥和 `.ionapi` 文件放入工单、截图或 Git 仓库。确认测试端点无法路由到生产环境。

## 配置 Infor API Gateway

1. 在 **Available APIs** 中，为目标环境创建一个 **Custom or Non-Infor** API 套件。请参阅 Infor 的 [API 套件说明](https://docs.infor.com/inforos/2025.x/en-us/useradminlib_cloud/apigatewayag_cloud/gyy1489512842881.html)。
2. 向套件添加一个端点，并填写已批准的 **Target Endpoint URL**。选择该端点所需的身份验证类型。对于 **API Key**，Infor 会要求填写 **Key Name** 和 **Key Value**；请使用 DocBits API 合约指定的名称，以及为此组织签发的密钥。请参阅 Infor 的[端点字段说明](https://docs.infor.com/inforos/2024.x/en-us/useradminlib_cloud/apigatewayag_cloud/bmg1489588707659.html)。请勿复制其他环境的密钥。
3. 按照 Infor 的[文档说明](https://docs.infor.com/ionapi/2021-x/en-us/ionapiag_cloud/tzr1489597424134.html)，在端点的 **Documentation** 设置下添加该环境的 OpenAPI/Swagger URL。请确认端点出现在 [API metadata](https://docs.infor.com/ionapi/latest/en-us/ionapiag_cloud/tdr1489674063627.html) 中。
4. 与 Infor 管理员一起，在将端点用于 ION 文档流之前，验证目标 URL、身份验证、代理路径，并执行安全的非生产调用。仅保存 API 套件并不能证明文档已送达。

## 在 DocBits 中配置导出

在目标 DocBits 组织中，打开 **Settings → Export**，然后选择 **New**。下方展示的英文 Sandbox Test A 组织没有已保存的配置。

![当前英文 DocBits Sandbox 导出列表，显示 New 操作且没有已保存的配置。](https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-7d6be575facf19bcca2afecb10568bb6973e6812%2Fdbdc-197-export-list-en.png?alt=media)

输入 **Configuration Title**，选择 **Document Type**，并仅在需要时选择 **Sub-Organization**。将 **Export** 设置为 **Infor**，并将 **Infor Type** 设置为 **Infor IDM + ION BOD**。当前表单随后会要求填写 **Deployment Type**（**CLOUD** 或 **ON-PREMISE**）、**ION API File**（`.ionapi`，必填）、**IDM Mapping File**（`.properties`）和 **BOD Mapping File**（`.properties`）。请向管理员获取这些特定于租户的文件。截图中有意将所有上传项留空。

![当前英文 DocBits Sandbox Infor IDM + ION BOD 导出表单，显示部署选项以及留空的 ION API、IDM 和 BOD 文件上传项。](https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-3d2880a0790e46b232099de20fce6d6078433e60%2Fdbdc-197-export-ion-bod-en.png?alt=media)

管理员验证 ION 路由后，保存配置并测试一份非生产文档。在 DocBits 和 Infor ION 中检查其状态。保存表单或 API metadata 条目并不能证明导出成功。


---

# 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/exporting-to-infor/creating-an-ion-api-endpoint.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.