Skip to main content

Introduction to Shirtigo Cockpit API

Welcome to the Shirtigo API documentation. This API allows you to integrate Shirtigo's print-on-demand, stick-on-demand, and fulfillment services directly into your applications.

Overview​

The Shirtigo Cockpit API provides programmatic access to our complete suite of services, enabling you to:

  • Manage product orders and fulfillment
  • Access print-on-demand services
  • Handle warehousing operations
  • Integrate branding solutions
  • Manage returns
  • Access personalization features

Key Features​

  • RESTful Architecture: Our API follows REST principles, making it intuitive and easy to integrate
  • Secure Authentication: Enterprise-grade security for all API endpoints
  • Comprehensive Integration: Full access to Shirtigo's service portfolio
  • Multiple Platform Support: Compatible with major e-commerce platforms including Shopify, WooCommerce, Shopware, PrestaShop, Amazon, eBay, and Etsy

Getting Started​

To begin using the Shirtigo Cockpit API, follow these steps:

  1. Create a Shirtigo Account – Sign up on Shirtigo Cockpit.
  2. Obtain API Credentials – Generate your API token in the dashboard
    • If the token is not displayed after creation, click the button again.
  3. Familiarize Yourself with REST APIs – Basic knowledge of HTTP methods (GET, POST, PUT, DELETE) is recommended.

Authentication​

All API requests require authentication. We use secure API keys to ensure the safety of your data and transactions.

The API key or OAuth2 access token is passed in the Authorization header:

Authorization: Bearer YOUR_API_KEY
Accept: application/json

Authorization is the only header that is evaluated. Other spellings, in particular Authentication, are ignored and result in a 401.

Base URL​

https://cockpit.shirtigo.com/api

Testing Your Integration​

There is no sandbox environment and no separate test mode. Integrations are developed against the live API. To build and test without triggering production or incurring costs:

  • Use a separate account for development and select prepayment as its payment method. Orders then remain in pending until payment is received, and no payment means no production and no cost.
  • Place orders with "is_onhold": true. Such an order is never handed to production until you release it via PUT /order/{reference}/release-onhold.
  • Cancel test orders via POST /orders/{reference}/cancel as long as they have not entered production.
  • Test webhooks without placing an order via POST /webhooks/{id}/test. It delivers a real, correctly signed request for an existing resource, marked with "mode": "test" in the payload.