A REST API is an interface with which external systems such as apps or servers can communicate through HTTP. With our REST API, you can build your own apps, websites, or plugins with web-to-print services. We handle production and shipping of the products for you.
You can connect with the REST API with almost every programming language. We have concise, technical documentation available for implementing a connection with the REST API. We offer code libraries for several programming languages.
We specialise in custom products! Thanks to our extensive range of printing machines, we can offer a taylor made product for almost every printing need. Contact us for an obligation free quote. If you have a unique concept, a non-disclosure agreement is possible.
Connecting with Print API is free. You only pay for production, handling, and shipping.
The REST API offers two methods of payment. If you don't have a payment system yourself, you can handle customer payments with our built-in payment screen. If you prefer, you can also choose to receive an invoice yourself periodically.
Don't have a payment system? Let your customer pay with the REST API's built-in payment screen. Per order, you receive compensation: your selling price minus the costs for production, handling and shipping. You can set the price of each product individually.
You receive an invoice periodically for placed orders if you don't have a payment system yourself. If you choose this option, make sure that periodic invoice is checked in your preferences.
Initially, customer care is handled through your own application or website: you stay in contact with your customers. Print API manages production and shipping and naturally you can contact us if a problem occurs. You can call or email us and we will reply within one work day.
It is possible to outsource customer care to Print API. Contact us and you'll receive a price proposal within one work day.
We are always available per email or phone to help with connecting or answering other questions you might have. Feauture requests and feedback are more than welcome, so do contact us! You'll receive an answer within one work day.
We regularly expand our API with new features. Like many other API's, we guarantee backwards compatibility with the version number in the URL. We will notify you in advance if support for an older version expires. Your code will always be supported for six months at the least.
Books and magazines should be deliverd in PDF file format. For other products that don't contain more than one page such as posters and canvasses, we accept PNG and JPEG files beside PDF. Keep in mind that your files should comply with the file deliverance specifications.
Pay attention: Do you use a different color profile than sRGB? Contact us.
Make sure that the file always contains the specified bleed. The bleed is the area around the file that is cut off or folded. Make sure that the bleed is filled: in this way you avoid white edges. If you deliverd files in PDF format, we place the necessary cutting edges, bleed and or cropboxes ourselves.
With books, make sure you keep the shoulder in mind. This is the part between the spine and the front and back of the book that is pushed inwards and has a width of 1 cm.
For books, you should deliver two separate PDF files: one for the cover and one for the content. You should export the content as separate pages in the PDF file. See our example PDFs:
Pay attention: If your book contains more than the minimum of 24 pages, the book will naturally become thicker. As a result, the spine of the book will grow. Make sure that your cover PDF has the appropriate width for the chosen number of pages! You can calculate the appropriate width of the PDF as follows: basic width + (extra number of pages / 2 x paper thickness). You can find the basic width en paper thickness in the file deliverance specifications.
The REST API supports two ways of delivering files. You can either specify a URL where Print API can download the file while placing an order, or upload the files to the API automatically after placing the order. Read the relevant technical documentation for more information.
If the file you deliver does not meet the file deliverance specifications, the API generates an error that specifies what should be adjusted. Should this unexpectedly happen in the live environment, you automatically receive an email.