Start here instead: most new integrations should begin with the Editor API, which covers designing, ordering and fulfilling an order end to end. Even if you have your own product UI, the editors can run headlessly for many products; reach out and we will help you scope that path. Use the Order Submit API directly when your orders are composed entirely outside WHCC. The exception is webhooks: registration for every integration, including the Editor API, is documented in this section.
Our Order Submit API lets you order many of our products programmatically. We receive, produce and ship thousands of orders via our Order Submit API every day.
You'll need Order API credentials before you can access the API. Reach out with details on your project and the types of products you're looking for and we'll get you setup with what you need.
We have a sandbox environment available to use while you build your integration. You will need a different set of credentials for each environment.
Sandbox URL: https://sandbox.apps.whcc.com
Production URL: https://apps.whcc.com
All of the examples throughout this documentation points to the production URL.
All requests require the use of https.
The sandbox environment also lets you trigger webhooks on demand while you build your handler. See the Webhook Sandbox.
Make image assets accessible to WHCC by URI somewhere, such as Amazon S3. Optionally leverage signed URLs for additional security.
Authenticate and get an access token for importing and submitting your order request against the correct WHCC account.
Generate an order request as structured JSON defining your order based on our JSON product catalog.
Import your JSON order request and sanity-check the order contents response.
Submit your order for production using a ConfirmationID returned when importing your order request.
Register to receive and then consume webhooks from WHCC as your order is processed and then shipped.
Get started with Authentication