# Amplifier integrations: orders and items

> Create an order, create an item and create an order source in Amplifier, and start a workflow when Amplifier sends “Order shipped”.

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

## Overview

Amplifier is an ecommerce fulfillment provider that stores inventory, ships orders for brands, and runs gift and offer campaigns. Tray.ai connects to Amplifier through the HTTP Connector, so your workflows can call the Amplifier API alongside the rest of your stack.

## Use cases

### Orders

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

- Create an order
- List orders
- Retrieve an order

### Items

Read and create items in Amplifier from any Tray.ai workflow. The Amplifier API covers calls such as create an item and list items.

- Create an item
- List items
- Retrieve an item

### Order sources

Read, create, and delete order sources in Amplifier from any Tray.ai workflow. The Amplifier API covers calls such as list order sources and create an order source.

- List order sources
- Create an order source
- Delete an order source

### Campaigns

Read, create, and update campaigns in Amplifier from any Tray.ai workflow. The Amplifier API covers calls such as list campaigns and get a campaign.

- List campaigns
- Get a campaign
- Create an offer

### Invoices

Read invoices in Amplifier from any Tray.ai workflow. The Amplifier API covers calls such as list invoices and get an invoice PDF.

- List invoices
- Get an invoice PDF

### Webhooks

Read, create, and delete webhooks in Amplifier from any Tray.ai workflow. The Amplifier API covers calls such as create a webhook and list webhooks.

- Create a webhook
- List webhooks
- Delete a webhook

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated Amplifier connector?

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