> 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/advanced-functions-and-tools/postman-for-docbits/test-your-bod-connection-with-postman.md).

# Test your BOD connection with Postman

## Overview

This page explains how to verify the successful processing of your BOD (Business Object Document) using Postman. You will test the relevant API endpoint by sending a request with your BOD mapping file. Follow the steps below to complete the process.

## Accessing Your API Key and BOD Mapping File

### Retrieving Your API Key

1. Go to **Settings → Global Settings → Integration & SSO**.

   <figure><img src="/files/xZMXlglpl5UGf01EAr79" alt=""><figcaption></figcaption></figure>
2. You can either manually copy your **API key** or click the copy button to copy it to your clipboard.

   <figure><img src="/files/Hgv5MK59mJb6Em4j2IM1" alt=""><figcaption></figcaption></figure>

### **Downloading the BOD Mapping File**

1. Go to **Settings → Document Processing → Export**.

   <figure><img src="/files/Y91OyluKfbGZLlzLEZlW" alt=""><figcaption></figcaption></figure>
2. In the **Actions** column of the relevant export entry, click the three-dot menu and select **Edit**.

   <figure><img src="/files/7VeLLyXW3VBpvcE3c405" alt=""><figcaption></figcaption></figure>
3. Locate the **BOD Mapping File** and click the **Download** button to save it.

   <figure><img src="/files/gB2RiogDI6Zdf9bLgK1n" alt=""><figcaption></figcaption></figure>

## Test the Endpoint in Postman

1. **Paste the cURL Command in Postman**

   Open Postman and paste the following cURL command into the **Import** section. Postman will automatically configure the request.

   ```bash
   curl -X 'POST' \
     'https://api.docbits.com/prod-api/import/purchase_order_bod' \
     -H 'accept: application/json' \
     -H 'X-API-KEY:' \
     -H 'Content-Type: multipart/form-data' \
     -F 'org_id=' \
     -F 'sub_org_id=' \
     -F 'file=@file.xml;type=text/xml' \
     -F 'custom_fields_mapping='
   ```

   <figure><img src="/files/muShZJgnAJILqzJOHqn5" alt=""><figcaption></figcaption></figure>

   <figure><img src="/files/ylnOWc4PcoQfETnzqBMd" alt=""><figcaption></figcaption></figure>
2. **Set the API Key**\
   Go to the **Headers** tab, locate the `X-API-KEY` header, and paste your API key into the **Value** column.

   <figure><img src="/files/F6DJpxPaAVXmWivT9OXp" alt=""><figcaption></figcaption></figure>
3. **Upload the BOD File**\
   Go to the **Body** tab, locate the `file` key, then click **Select Files** in the **Value** column and upload your BOD XML file.

   <figure><img src="/files/l1UHAlzk3YqJQjpJ7rzj" alt=""><figcaption></figcaption></figure>
4. **Send the Request**\
   Click **Send** to make the API call.

   <figure><img src="/files/o9tB0qwj3RViPqaKuCZw" alt=""><figcaption></figcaption></figure>
5. **Verify the Response**\
   Check the response to confirm that your BOD was processed successfully.

   <figure><img src="/files/B1Ru29RKDdCLN9V1tCFg" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.docbits.com/advanced-functions-and-tools/postman-for-docbits/test-your-bod-connection-with-postman.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.