> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stateset.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> 186 native integrations across marketplaces, 3PLs, ERP, and support — what's connected and how.

# Integrations

An agent is only as useful as the systems it can reach. StateSet ships **186 native
integrations** through the [Sync Server](/stateset-sync-server-api-basics), covering sales
channels, fulfillment, ERP, and support.

Anything without an API at all is still reachable — [Computer Use](/computer-use-agent) drives
the UI.

## Sales channels and marketplaces

Shopify · BigCommerce · WooCommerce · Adobe Commerce · Shopware · Amazon · eBay · Etsy ·
Walmart · TikTok Shop · Temu · SHEIN · Alibaba · MercadoLibre · Rakuten · Coupang · Lazada ·
Shopee · Flipkart

## 3PL, WMS, and fulfillment

ShipBob · ShipHero · ShipMonk · Deposco · Extensiv (3PL Central) · Logiwa · Infoplus · Monta ·
Byrd · Bleckmann · DCL · Cart.com · Capacity · Cybership · Bigblue · Luminous · VeraCore ·
Mintsoft · Quiver · Red Stag · Visible SCM · Expeditors · Stord · Whiplash · UNIS · NRI ·
MasonHub · Flexport

Counting platform-backed vendors, roughly **155 3PL/WMS integrations** are available in total.

## ERP, finance, and operations

NetSuite · Fishbowl · Xero · plus the ledger, AP, and AR surfaces of the
[iCommerce finance layer](/stateset-icommerce/stateset-icommerce-finance).

## Support, subscriptions, and marketing

Gorgias · Zendesk · Recharge · Stay · Skio · Loop Returns · Klaviyo · SendGrid · AfterShip ·
Algolia

## Trading partners (EDI)

For retailers and 3PLs that exchange documents rather than call APIs,
[StateSet EDI](/stateset-edi/overview) covers X12 and EDIFACT — 24 transaction sets across five
transports, with 40+ packaged retailer connectors.

## Not all integrations are equal

<Warning>
  Before planning an onboarding, check the integration's **verification status**. They fall into
  three groups:

  * **Verified** — the client implements the vendor's documented API, auth and endpoints.
  * **Platform-backed** — the vendor runs a WMS already integrated; use that service with
    vendor-issued credentials.
  * **Partner-only** — no public API documentation. The spec arrives during vendor onboarding, and
    some vendors have no REST API at all (Coghlan is CSV-over-FTP; ITS Logistics uses private push
    APIs plus EDI).

  The full matrix is in [Sync Server: What's New](/stateset-sync-server-whats-new#verification-status).
</Warning>

## How integrations are driven

| Path                                                           | Use when                                                      |
| -------------------------------------------------------------- | ------------------------------------------------------------- |
| [Sync Server API](/stateset-sync-server-api-basics)            | Server-to-server sync of orders, inventory, products, returns |
| [Sync MCP](/stateset-sync-mcp)                                 | An agent should drive sync directly, per tenant               |
| [iCommerce](/stateset-icommerce/stateset-icommerce-quickstart) | The engine is embedded in your runtime                        |
| [Computer Use](/computer-use-agent)                            | The system has no API                                         |

Adding a system is **data, not code** — one connector plus its capability rows. Dispatch,
idempotency, review gates, and spend caps then apply automatically by
[risk tier](/next-temporal/connectors#risk-tiers).

## Connecting one

List what a tenant already has configured:

```bash theme={null}
curl "https://api.stateset.com/v1/tenants/$TENANT/integrations" \
  -H "x-stateset-api-key: $SYNC_API_KEY"
```

Configure a channel — credentials are supplied per tenant, never global:

```bash theme={null}
curl -X POST "https://api.stateset.com/v1/tenants/$TENANT/integrations" \
  -H "x-stateset-api-key: $SYNC_API_KEY" \
  -H 'content-type: application/json' \
  -d '{
    "service": "shopify",
    "enabled": true,
    "credentials": { "shop": "acme.myshopify.com", "access_token": "shpat_..." }
  }'
```

Then run a sync and check the result:

```bash theme={null}
curl -X POST "https://api.stateset.com/v1/tenants/$TENANT/sync/orders" \
  -H "x-stateset-api-key: $SYNC_API_KEY"
```

Responses use the standard envelope — `{ "meta": { "requestId": … }, "data": … }` on success and
`{ "meta": …, "error": { "code": …, "message": … } }` on failure. Order creation is idempotent on
`shopify_order_id`, and write endpoints accept an `idempotency-key` cached for 24 hours, so a
retried call replays rather than duplicating.

<Tip>
  An `integration_missing` error code means the service isn't configured for that tenant — check
  the list call above before debugging credentials.
</Tip>

## Related

* [Sync Server API Basics](/stateset-sync-server-api-basics)
* [Connectors & Capabilities](/next-temporal/connectors)
* [StateSet EDI](/stateset-edi/overview)