> For the complete documentation index, see [llms.txt](https://docs.optondemand.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.optondemand.com/integrations-and-apps/rest-api/user-guides/create-api-integration.md).

# Create API Integration

Connect your system to OPT OnDemand Smart Fulfillment Center

{% hint style="warning" %}
To establish an API integration, you must possess a **customer account** and assigned **portfolio of products** and **services**. Contact our sales department (**<ecom-sales@optondemand.com>)**, who will provide comprehensive guidance throughout the entire process. Upon completing the initial phase, you will be provided with all the requisite data to initiate the integration development.
{% endhint %}

Once the above is completed you will be provided with set of credentials to authenticate and authorize yourself against the Rest API. For more info see [Authentication](/integrations-and-apps/rest-api/api-structure/authentication.md)

## Developing and testing the integration

For development and testing purposes set flag `isTest` in order data payload to `true`. This way you can submit as many orders as you like. These orders will not be submitted to actual OPT OnDemand Smart Fulfillment center for production or fulfillment. For more info about testing, see [Create Order](/integrations-and-apps/rest-api/api-structure/orders/create-order.md) API specification page.

To list order you submited as test, make sure you include this flag in the Get orders request as well. See [Get Orders](/integrations-and-apps/rest-api/api-structure/orders/get-orders.md) for more details.

&#x20;Once you are done with testing, remove this flag or set it to `false`.


---

# 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.optondemand.com/integrations-and-apps/rest-api/user-guides/create-api-integration.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.