# Sellercloud integrations: orders and customers

> Update order shipping status, create a customer and create a purchase order in Sellercloud.

**Canonical page:** https://tray.ai/connectors/sellercloud-integrations/
**Categories:** E-commerce
**Connects through:** HTTP Connector

## Overview

Sellercloud is an ecommerce operations platform for multichannel sellers, handling orders, inventory, product catalogs, purchasing, and warehouse fulfillment. Tray.ai connects to Sellercloud through the HTTP Connector, so your workflows can call the Sellercloud API alongside the rest of your stack.

## Use cases

### Orders

Read, update, and delete orders in Sellercloud from any Tray.ai workflow. The Sellercloud API covers calls such as get all orders and delete an order.

- Get all orders
- Delete an order
- Update order shipping status

### Customers

Read, create, and update customers in Sellercloud from any Tray.ai workflow. The Sellercloud API covers calls such as get all customers and get a single customer.

- Get all customers
- Get a single customer
- Create a customer

### Purchase orders

Read, create, update, and manage purchase orders in Sellercloud from any Tray.ai workflow. The Sellercloud API covers calls such as create a purchase order and get all purchase orders.

- Create a purchase order
- Get all purchase orders
- Update a purchase order

## Challenges Tray.ai solves

### Keeping Sellercloud credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Sellercloud credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Sellercloud API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Sellercloud API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Sellercloud?

Yes. Tray.ai connects to Sellercloud through the HTTP Connector, which calls the Sellercloud API directly. Any call the Sellercloud API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Sellercloud?

The Sellercloud API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Sellercloud connector?

Sellercloud runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Sellercloud connector from the Sellercloud API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/
