Posts in: API & integration
23/10/2008

ZetaPrints provides direct connection to its back-end via web-to-print Aplication Programming Interface or API. It allows customers to add new specific features, replace screens or bypass ZetaPrints user interface altogether. Doing so requires considerable IT skills. More »

30/05/2010

By default web-to-print text fields only replace the text with user input. ZetaPrints web-to-print may change the appearance of the text automatically (wrapping, font resizing). This post explains how to add field manipulation metadata for user-defined editing, such text color, shift, etc. More »

31/03/2009

Image resizing on the client doesn’t always produce good quality images.  E.g. previews or photo thumbs may need to be resized on the fly to fit the page layout. Appending the required image size to the file name instructs ZetaPrints dynamic image generator to serve the requested image in the specified dimensions. More »

27/03/2009

A user can be logged into your web-to-print portal automatically by passing required parameters in the referral request. This feature is only available if you know user ID and password.

More »

26/04/2009

This web-to-print API return a list of all web-to-print catalogs per site. It comes useful if you want to import data or synchronise databases.

More »

31/03/2009

ZetaPrints web-to-print system can be used for template based dynamic imaging. This interface is simplified for preview-only process. An open-source e-cards plugin is hosted under Google Code and utilizes this API. More »

25/06/2010

The API key is available to holders of master (printer, publisher, business) account only. More »

28/01/2010

This set of API calls provides basic image editing capabilities for web-to-print and dynamic imaging. Only images from user libraries can be edited. The actual hi-res image is not available for downloading or preview. More »

22/01/2010

Web-to-print users can upload images into their image libraries to be used in templates. Once an image is uploaded it is validated to be of an accepted type and a small preview is generated. The preview is usually within 600px x 600px. Uploaded images cannot be downloaded.

We offer a set of web-to-print API functions to upload and manipulate the images. More »

30/05/2010

By default web-to-print image fields only replace the placeholder image with a user image. ZetaPrints web-to-print may change the appearance of the image automatically (rotating, filters, etc) to match the placeholder. This post explains how to add image manipulation metadata for user-defined editing, such cropping, shift, resizing, etc. More »

27/03/2009

Printer authentication during web-to-print API calls is controlled by ApiKey parameter which is unique and is not supposed to be shared. User access via API and control of user accounts requires an MD5 hash of the caller’s IP and the user’s password as one of parameters. This post explains how the hash should be calculated. More »

23/10/2008

Web to print orders API gives direct access to list of orders, their details and all associated resources. One of applications is to download new orders automatically and process the files on the client side, including automatic pre-flight, hot folder routing, data import into MIS and accounting s/w. More »

16/04/2009

A saved web-to-print order has no output files other than the preview files. An external web-to-print system may request ZetaPrints web-to-print to generate the final order for a given saved order.

More »

16/04/2009

Web to print orders API gives direct access to list of orders, their details and all associated resources. One of applications is to download new orders automatically and process the files on the client side, including automatic pre-flight, hot folder routing, data import into MIS and accounting s/w. More »

16/04/2009

This interface gives direct access to all web-to-print order details by OrderID. More »

12/09/2009

Creating a new web-to-print order via API is a 3-stage process:

  • generate previews
  • save an order
  • generate output files

This API function creates a “saved” web-to-print order for a template using the latest data from the user cache and the previews generated by the web-to-print user earlier. More »

16/04/2009

A web-to-print order has a status, changed to which are logged and help determine the lifecyle of the order. The status needs to be set to “deleted” for orders to be removed from our web-to-print database.

More »

27/05/2009

Customer payments can be processed by PayPal directly or by any other custom gateway via API. You can accept payment for your web-to-print and dynamic imaging services via any payments provider as long as you implement a gateway. More »

07/10/2009

Search for templates may return no or unsatisfactory results. It can be complemented by searching for matching keywords and presenting them as additional web-to-print search options to the user. More »

05/08/2009

This set of web-to-print API calls allows to do search directly from other websites. Web-to-print templates can be searched by keywords, size and output type. Web-to-print search results come back as an RSS feed with a list of templates, same as for a list of templates returned for a catalog. More »

12/06/2010

Dynamic imaging shapes can be located on the preview image using relative coordinates as explained in Shape metadata post. ZetaPrints dynamic imaging and web-to-print system accepts a number of parameters with every text and image field to move/crop/resize the shapes they are in. This post explains how the coordinates should be calculated.

The coordinate system

All coordinates are relative to width and height of the preview, where x1:0,y1:0 (top left) and x2:1,y2:1 (bottom right). A shape has 2 sets of coordinates:

  • box-x1, box-y1, box-x2, box-y2 – default preview
  • box-x1-u, box-y1-u, box-x2-u, box-y2-u – updated preview

As many shapes are transformed automatically depending on the contents the two sets can differ considerably. Even the actual size and proportions of the preview may differ. They can be normalized using page coordinates as the reference point. See attributes of TemplateDetails/Pages/Page element (page2box-x, page2box-y, page2box-w, page2box-h) for page to default preview relationship and page2box-x-u, page2box-y-u, page2box-w-u, page2box-h-u for page to updated preview relationship.

Page is the known point of reference

ZetaPrints dynamic imaging is stateless when it comes to preview generation. It remembers some of the details of the last call, but as the processing is distributed this info may not be readily available. It is more reliable if all coordinates in the metadata are specified in relation to a stable point of reference, which is the top left of the page. Read more about page to preview relationship in Shape metadata post.

When the default preview is showing for the first time the state of the template and the position of the shapes is known to ZetaPrints web-to-print system and the next request can be processed with it as reference point. However, further on as more previews are generated the shapes and the preview image itself flex and change size. The only stable reference point known to ZetaPrints and the script on the client is the page itself.

Coordinates normalization

All coordinates and distances submitted in metadata parameters need to be in reference to the page, not the preview. The client side script need to recalculate them.

Calculation example

From template details XML: box-x1-u = 0.25, page2box-x-u=-0.25, page2box-w-u=0.75

Position on the page = ([box-x1-u] – [page2box-x-u]) /[page2box-w-u] = (0.25 – (-0.25))/0.75=0.6666

Shift left by 30% of the last preview width: sh-x=shift / [page2box-w-u] = 0.30/0.75=0.4

12/06/2010

Web-to-print templates contain information about shape and field position, alignment, anchor points and other metadata to assist with client side scripting and interactive editing in dynamic imaging and web-to-print applications. This post describes some of the metadata parameters and concepts. More »

13/02/2009

Extended web to print template details can be requested as XML via HTTP GET. You may need this function to show the template in your own web-to-print user interface bypassing ZetaPrints screens altogether. More »

27/03/2009

Our web to print software allows user access control via API. Access is controlled per web-to-print catalog with GRANT and DENY calls.

More »

29/01/2009

ZetaPrints web-to-print API allows creating of new users and updating details of existing ones. More »

27/03/2009

Users can be registered via API with a minimal level of detail to enable their access without logging in. More »