Building with the Merch API

A short tour of the REST API and webhooks. Pick the article that maps to what you want to do.

Last updated May 8, 2026

The Merch REST API lets you read and write orders, products, inventory, campaigns, and contacts from your own systems, and subscribe to webhooks for event-driven updates.

#Who this is for

You are integrating Merch into another application — a CRM, an HR onboarding flow, an internal store, a fulfillment dashboard, or a custom tool. If you are managing orders by hand in the customer portal, the customer-facing categories are a better fit. The articles here assume you are writing code.

#What you can do

  • Orders — list, fetch, create, and cancel fulfillment orders. Pick a warehouse to route from. Track shipment status.
  • Products — list active product variants and their SKUs, dimensions, weights, and minimum order quantities.
  • Inventory — read on-hand, available, allocated, and inbound stock per warehouse, plus the underlying inventory event log.
  • Campaigns — list the campaigns on your account. Order creation and invites both reference a campaignId.
  • Invites and contacts — add contacts to a campaign and send personalized invites by email or with a redemption URL.
  • Webhooks — subscribe to event notifications for order and invite lifecycle changes. Each delivery is signed with HMAC-SHA256 so you can verify it came from Merch.

#How requests work

The base URL is https://api.merch.com. All routes are mounted under /v1. Every request needs a Authorization: Bearer <your_api_key> header. Request and response bodies are JSON.

#Where to start

Ready to elevate your merch?

Custom design, production, campaigns, and global fulfillment — one partner, zero platform fees. Your custom proposal in 24 hours.