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

# REST API

Unlimited access to the OPT Smart Fulfillment

Our API enables full integration with the entire OPT Smart Fulfillment system, providing unrestricted access to all its features. It is the ideal solution for customers seeking to automate their operational processes and eliminate manual intervention.

## Key Features

✅ **Print what ever you want:** Send to custom print orders where you can define all prints and customizations during the order submission process.&#x20;

✅ **Easy order submission of existing products:** Send the orders for predefined products just by using ean13.

✅ **Manage your product portfolio:** Get all information about your existing products, including previews and stock level information.&#x20;

✅ **Master your shipping:** You are the one who decides what shipping will be used for each order. You can also include your own shipping labels. &#x20;


---

# 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.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.
