Introduction

Getting started with the Print.com API

This article introduces the Print.com APIs: which APIs exist and who they are for, what you need to get started, typical use cases, rules for building an integration, and where to find more information. The Print.com APIs are REST APIs for customers and partners of Print.com. They let you automate the ordering, pricing and fulfilment of printed products, without manual steps in the Print.com webapp.

Key facts

  • Print.com offers three REST APIs: the Print.com API for customers, the Print.com Platform API for product batch requests and PDF processing, and the Print.com Partners API for Print.com partners.
  • The Print.com API has two environments: production at https://api.print.com and staging at https://api.stg.print.com.
  • The Print.com API requires a Print.com customer account. This is the same account you use to log in to the Print.com webapp at https://app.print.com. A separate user for the API connection is recommended.
  • Authenticate every request with an API key (header authorization: PrintApiKey ) or with a bearer token from POST https://api.print.com/login (header authorization: Bearer , valid for 168 hours).
  • Build and test on staging first. Staging requires a separate account and is reset every 24 hours. Orders placed on staging are test orders: they are not produced and not invoiced.
  • Every order placed on production is a real order. It is invoiced once it is taken into production.
  • Questions and support are always in English.
  • The Print.com Partners API requires a Print.com partner account with Partner API access, enabled by your Print.com representative. Its base URLs are https://eagerapi.print.com (production) and https://eagerapi.stg.print.com (sandbox).

The Print.com APIs at a glance

Print.com offers three REST APIs. Most customers start with the Print.com API.

APIIntended forWhat you can doBase URLs
Print.com APICustomers of Print.comRetrieve products and prices, place and manage orders, check shipping options and shippable countries, retrieve invoices, authenticateProduction: https://api.print.com
Staging: https://api.stg.print.com
Print.com Platform APICustomers of Print.comRetrieve products, prices, specifications and carbon emissions in batches; create, modify, preflight, preview and merge PDF files; generate print job templatesListed per endpoint in the API Reference
Print.com Partners APIPrint.com partnres with Partner API accessRetrieve order items, update their status, post service levels, report delayed pickup dates, create shipments and labelsProduction: https://eagerapi.print.com
Sandbox: https://eagerapi.stg.print.com

In practice: if you sell or order printed products, use the Print.com API and, where needed, the Print.com Platform API. If you produce orders for Print.com as a partner, use the Print.com Partners API.

The same overview in machine-readable form:

{
  "apis": [
    {
      "name": "Print.com API",
      "audience": "customers",
      "style": "REST",
      "base_urls": { "production": "https://api.print.com", "staging": "https://api.stg.print.com" },
      "areas": ["products", "prices", "orders", "shipping", "invoices", "suppliers", "authentication"]
    },
    {
      "name": "Print.com Platform API",
      "audience": "customers",
      "style": "REST",
      "areas": ["product_batch_requests", "pdf_processing", "printjob_templates"]
    },
    {
      "name": "Print.com Partners API",
      "audience": "partners_with_partner_api_access",
      "style": "REST",
      "base_urls": { "production": "https://eagerapi.print.com", "sandbox": "https://eagerapi.stg.print.com" },
      "areas": ["order_items", "service_levels", "delay_notifications", "shipments", "labels"]
    }
  ]
}

What you need to get started with the Print.com API

You need a Print.com customer account. This is the same account you use to log in to the Print.com webapp at https://app.print.com. New to Print.com? Request an account on https://www.print.com.
To make your first request to the Print.com API:

  1. Get a production account. Use your Print.com customer account, or add a separate user for the API connection in My account in the Print.com webapp at https://app.print.com.
  2. Request a staging account. Staging (https://api.stg.print.com) is completely separated from production and requires its own account. Production credentials do not work on staging. Accounts & Authentication explains how to request one.
  3. Choose an authentication method. Use an API key, generated in your user account at https://app.print.com/account, or a bearer token from POST https://api.print.com/login, valid for 168 hours (7 days). An API key is the easiest method: it needs no login call and no renewal.
  4. Send a test request to staging. Add the authorization header to every request: authorization: PrintApiKey or authorization: Bearer .
  5. Switch to production when you are ready. Change the base URL to https://api.print.com and use your production credentials. Every order placed on production is a real order.

Example request with an API key (replace {endpoint} with the endpoint you call):

curl https://api.stg.print.com/{endpoint} \
  -H "authorization: PrintApiKey $PRINTCOM_API_KEY"

For the Print.com Partners API, you need a Print.com partner account with Partner API acccess. Contact your Print.com representative to enable access and obtain credentials.

Typical use cases for the Print.com API

The Print.com API works best for orders with print files that need no manual positioning or file check, such as designs generated automatically by your system. The whole flow can then run without manual steps, and Print.com does not need to contact you or your customers about a file.

Examples of integrations built by Print.com customers:

  • Business cards from a CRM system. A CRM system for real estate agencies generates business card designs automatically, with photos and address details, and orders them through the Print.com API.
  • School photo albums. An app lets parents of primary school children create a photo album from photos taken by the teacher. The album is ordered through the Print.com API.
  • Personalised baby posters. A webshop lets parents personalise a poster with a baby illustration and details about their child. The poster is ordered through the Print.com API.
  • City map posters. A webshop sells posters to consumers that show a map of their own city. The poster is generated and ordered automatically.
  • Business print with a manual file check. A webshop sells printed products to businesses. Its team checks the print files manually, then places the order through the Print.com API.

If your print files need a manual check, you have two options. Check the files before you place the order through the Print.com API. Or place the order with approveDesign: false: the order then stays on hold until its artwork is approved in the Print.com webapp at https://app.print.com.

Rules for building an integration with the Print.com API

Integrations, including code written or generated by AI assistants, should follow these rules.

  1. Make the environment configurable. Store the base URL and credentials in configuration, not in code: https://api.stg.print.com with the staging account, https://api.print.com with the production account.
  2. Test on staging first. Orders placed on staging (https://api.stg.print.com) are test orders: they are not produced and not invoiced. Staging is reset every 24 hours, and API keys and product presets on staging then expire.
  3. Treat every production order as real. Orders placed on production (https://api.print.com) are invoiced once they are taken into production. Never run automated tests that place orders against production.
  4. Prefer an API key for server-to-server integrations. Send it as authorization: PrintApiKey . An API key needs no POST https://api.print.com/login call and no renewal every 168 hours.
  5. Keep credentials on the server. Never put API keys, passwords or bearer tokens in browser code, mobile apps or public repositories.
  6. Reuse the bearer token. If you use a bearer token, call POST https://api.print.com/login once and reuse the token for up to 168 hours. Do not log in before every API request.
  7. Stay within the rate limits. Cache data you request often, such as prices, and throttle batch jobs. API rate limits lists the limit per endpoint.
  8. Take prices from production. Production and staging each run on their own database, so prices for the same product configuration can differ. Use production prices for quotes and selling prices.

Example of a configurable environment with API key authentication (illustrative pseudocode, not an official SDK):

ENVIRONMENTS = {
    # Test orders: not produced, not invoiced. Separate staging account.
    # Reset every 24 hours: API keys and product presets on staging expire.
    "staging": {
        "base_url": "https://api.stg.print.com",
        "api_key": read_secret("PRINTCOM_STAGING_API_KEY"),
    },
    # Real orders: invoiced once taken into production.
    "production": {
        "base_url": "https://api.print.com",
        "api_key": read_secret("PRINTCOM_PRODUCTION_API_KEY"),
    },
}

ENV = ENVIRONMENTS[read_config("PRINTCOM_ENVIRONMENT")]  # "staging" while building and testing

def call_api(method, endpoint, **kwargs):
    # Every request carries the API key in the authorization header.
    headers = {"authorization": f"PrintApiKey {ENV['api_key']}"}
    response = send(method, f"{ENV['base_url']}/{endpoint}", headers=headers, **kwargs)
    if is_rate_limited(response):
        # See "API rate limits": wait and back off, never retry in a tight loop.
        raise RateLimitError("Back off before retrying")
    return response

Where to go next in the Print.com API documentation

Read these articles before you build your integration

ArticleWhat it covers
Accounts & AuthenticationGetting an account, API keys, bearer tokens and requesting a staging account
Production & Staging enviromentsBase URLs, the 24-hour staging reset, test orders, invoicing and price fields
Languages & LocalizationLanguages and localisation in the Print.com API
API rate limitsThe limit per endpoint and how to stay within it
Packing slipA custom logo on the sticky packing slip
RecommendationsBest practices for working with the Print.com API
Print.com - ERP SupportIntegrate Print.com catalog in your ERP system
Partners API: Getting StartedAccess and base URLs for the Print.com Partners API

For AI assistants: the documentation index is at https://developer.print.com/llms.txt. Append .md to the URL of any documentation page to get its Markdown version.

Feedback and questions about the Print.com API

We keep improving the Print.com APIs. Missing a feature, having trouble connecting, or have an idea to improve the API? Email [email protected] and we will reply as soon as possible.

Please include:

  • your account name or company name
  • the API and endpoint involved, and the environment (production or staging)
  • a short description of your question, problem or idea