> For the complete documentation index, see [llms.txt](https://help.orderdesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orderdesk.com/start-here/learn-the-basics/what-are-integrations.md).

# What Are Integrations?

> New to Order Desk? Order Desk collects all your orders from all your sales channels in one place and sends them to your chosen fulfillment services automatically.
>
> <i class="fa-computer" style="color:$primary;">:computer:</i> [See all integrations](https://www.orderdesk.com/integrations/) . <i class="fa-wallet" style="color:$primary;">:wallet:</i> [Pricing](https://www.orderdesk.com/pricing/) . <i class="fa-arrow-right" style="color:$primary;">:arrow-right:</i> [Start free trial](https://app.orderdesk.me/account-setup)

Software integrations allow different applications to connect and share data. In ecommerce, they’re most often used to move key information like order details, customer data, shipping and tracking info, and inventory levels between platforms automatically.

### Watch And Learn

Visual learner? Here’s a video explaining how integrations work on Order Desk.

{% embed url="<https://vimeo.com/604143848?fe=cm&fl=pl>" %}

### How Do They Work?

Each piece of software is built with its own internal systems and terminology. Let’s look at two fulfillment companies as an example:

*Donut Warrior* and *Bunches Of Bagels*. Both offer 2-3 day expedited shipping options, but *Donut Warrior* calls theirs “Glazing Fast” while *Bunches of Bagels* calls the same shipping option “Toasted Turbo”. If a store has sold an item via their sales channel that included expedited shipping under a third name, none of the services would immediately understand which shipping option to assign to the order.

That’s where an API integration comes in handy.

### What Is An API?

An **API**, or Application Programming Interface, is what allows one service to make parts of its data available in a structured way. APIs define what information can be shared and how other software should request it. Here’s an example of what data might look like via an API:

![](https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2FOVODPbjpuXus40d4k8uA%2Flegacy-3952d25c16b36c6f5b9a.png?alt=media)

An integration will take that data and present it in a way that is easier to understand, essentially acting as a translator for the raw data. The API allows another piece of software to access to specific data in its system, and the integration is what translates it into something other systems can use.

Order Desk builds the majority of its integrations by connecting to their APIs, though some older services use a different method for sharing data: **EDI**, or Electronic Data Interchange. EDIs are often found in industries like manufacturing and freight, and while they aren’t commonly used with Order Desk, they serve a similar purpose: standardizing how businesses share data between systems.

### Need Help?

If you have any questions about any of the information in this guide, we’re here to help!

[Click here](https://www.orderdesk.com/contact) to email Order Desk support.


---

# 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://help.orderdesk.com/start-here/learn-the-basics/what-are-integrations.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.
