# Shipday integrations: delivery orders

> Add a carrier and assign a delivery provider in Shipday, and start a workflow when Shipday sends “Order assigned”.

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

## Overview

Shipday is delivery management software for restaurants, couriers, and retailers that dispatches orders to drivers or delivery services and tracks them live. Tray.ai connects to Shipday through the HTTP Connector, so your workflows can call the Shipday API alongside the rest of your stack.

## Use cases

### Delivery orders

Read, update, and manage delivery orders in Shipday from any Tray.ai workflow. The Shipday API covers calls such as retrieve active orders and insert an order.

- Retrieve active orders
- Insert an order
- Edit an order

### Pickup orders

Update, delete, and manage pickup orders in Shipday from any Tray.ai workflow. The Shipday API covers calls such as insert a pickup order and edit a pickup order.

- Insert a pickup order
- Edit a pickup order
- Delete a pickup order

### Carriers

Read and create carriers in Shipday from any Tray.ai workflow. The Shipday API covers calls such as retrieve carriers and add a carrier.

- Retrieve carriers
- Add a carrier

### On-demand delivery

Read and update on-demand delivery in Shipday from any Tray.ai workflow. The Shipday API covers calls such as check availability and assign a delivery provider.

- Check availability
- Assign a delivery provider

### Shipday events

Start a Tray.ai workflow the moment something happens in Shipday. Shipday sends events such as order assigned and order picked up to a Tray.ai webhook trigger.

- Order assigned
- Order picked up
- Order on the way

## Challenges Tray.ai solves

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

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

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

The Shipday 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 Shipday connector?

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