> 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/infor-integration-and-configuration/importing-customer-master-data/importing-via-the-api.md).

# Importing via the API

Sending master data into DocBits by hand using the API

Master data normally reaches DocBits automatically through your ION data flow. The pages in this section describe how to send the same data in by hand using the API test interface — useful when you want to re-import a record, load something that never arrived, or try a new field mapping before switching the automatic flow on.

Each page follows the same five steps: open the API link for your environment, authorize with your Org ID and API key, fill in the form, execute, and check that the data arrived.

* [Import Suppliers (Supplier BOD)](/infor-integration-and-configuration/importing-customer-master-data/importing-via-the-api/supplier-bod.md)
* [Import Purchase Orders (Purchase Order BOD)](/infor-integration-and-configuration/importing-customer-master-data/importing-via-the-api/purchase-order-bod.md)
* [Import Goods Receipts (Receive Delivery BOD)](/infor-integration-and-configuration/importing-customer-master-data/importing-via-the-api/receive-delivery-bod.md)
* [Import Master Data from XML](/infor-integration-and-configuration/importing-customer-master-data/importing-via-the-api/master-data-xml.md)

## What you need

* **An API key** — see [API Key Management](/administration-and-setup/settings/global-settings/integration/api-key-management.md).
* **Your Org ID** — under **Settings → Integration & SSO** in the **ID** section.
* **The data itself**, as an XML file or as XML content you can paste.

{% hint style="warning" %}
An import writes straight into your organization's master data. Check which environment, which region and which organization you are pointing at before you execute.
{% 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/infor-integration-and-configuration/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.