# Shippo integrations: shipments and transactions

> Create a shipment, create an address and create a batch in Shippo, and start a workflow when Shippo sends “Tracking updated”.

**Canonical page:** https://tray.ai/connectors/shippo-integrations/
**Categories:** Supply chain
**Connects through:** HTTP Connector

## Overview

Shippo is a multi-carrier shipping service for online sellers, used to compare carrier rates, buy and print labels, validate addresses, and track parcels. Tray.ai connects to Shippo through the HTTP Connector, so your workflows can call the Shippo API alongside the rest of your stack.

## Use cases

### Shipments

Read and create shipments in Shippo from any Tray.ai workflow. The Shippo API covers calls such as create a shipment and get shipment rates.

- Create a shipment
- Get shipment rates

### Transactions

Read transactions in Shippo from any Tray.ai workflow. The Shippo API covers calls such as buy a shipping label and get a transaction.

- Buy a shipping label
- Get a transaction

### Addresses

Create addresses in Shippo from any Tray.ai workflow. The Shippo API covers calls such as create an address and validate an address.

- Create an address
- Validate an address

### Batches

Read and create batches in Shippo from any Tray.ai workflow. The Shippo API covers calls such as create a batch and get a batch.

- Create a batch
- Get a batch
- Add shipments to a batch

### Tracking

Read tracking in Shippo from any Tray.ai workflow. The Shippo API covers calls such as get a tracking status and register a tracking number.

- Get a tracking status
- Register a tracking number

### Orders

Read and create orders in Shippo from any Tray.ai workflow. The Shippo API covers calls such as create an order and list orders.

- Create an order
- List orders

## Challenges Tray.ai solves

### Keeping Shippo 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 Shippo 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 Shippo 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 Shippo 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 Shippo?

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

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

The Shippo API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Shippo connector?

Shippo runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Shippo connector from the Shippo 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/