Receiving Jobs
Once a Job is ready for production, it can then begin to be picked up a Production House / Supplier.
This is usually indicated by the Job status job.production.queued
which means it has passed Pre-Press and preflighting checks and has been fully handed over to the next Client in the job's lifecycle.
When all Jobs are in this status, the Batch moves to job_batch.production.ready
. This is indicates that all Jobs have left Pre-Press and is now in the hands of Production.
Job status transitions come through as a job.status.transition
event, whilst Batch status transitions come through as job_batch.status.transition
.
Job Information
The Job payload contains all the entire job spec, including all finishings.
Job Batch Information
The Job Batch will contain all Jobs to be shipped out together. An example payload of two Jobs in a Job Batch:
It's important to note that when receiving a webhook, regardless of webhook event type, we will always provide lightweight versions of objects. If the information you require is not available in the webhook event itself, then you must use the API to receive the fully populated objects instead.
Artwork
PrintedDirect will always return print-ready artwork which has been approved by the Pre-press client.
Each component will have its own Artwork object with a status and its corresponding ArtworkFiles attached to specific finishings. This allows us to provide different artwork files for different parts of the Job. For example, a foiling Job has multiple artwork files (cmyk, foil-only, etc).
Downloading
In order to download the artwork, you must request the downloadable URL via an authenticated API endpoint:
GET /1.0/files/e6a76cb2-d12f-499f-a620-60a5104ffa31/download
This will return a 302 Found
response with the URL of the file.
If you want to retrieve a standard 200 OK
response with a JSON payload containing the URL (i.e. without the redirect response), you can use the following instead:
GET /1.0/files/e6a76cb2-d12f-499f-a620-60a5104ffa31/download-path