Artworker API

Name: Artworker API API
Brand: Artworker API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage ProcessingapiKey19 EndpointsREST

For Agents

Drive Artworker print and packaging workflows: create jobs, request artwork, attach files, run task workflows, and listen for events via webhooks.

Quickstart

Get started with Artworker API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create an Artworker artwork job"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Artworker API API.

Create new artwork jobs and look up job items

Mark job items complete, archive them, or request artwork from a supplier

Import and attach files to a job item, including referencing files by custom uid

Drive task-based workflows: list workflows, fetch tasks, attach files and pages

GET STARTED

Start building with Artworker API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Artworker API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Artworker API, keeping it validated and agent-ready. Artworker is a print and packaging artwork management platform, and its open API exposes job items, file imports and proofing, workflow tasks, task files and pages, and webhook endpoints. Nineteen endpoints span the v2 job lifecycle (create job, complete or archive job items, request artwork, attach files) and the v1 task and webhook surface used to drive longer-running production workflows.

Use Cases

Patterns agents use Artworker API API for, with concrete tasks.

★ Print Job Intake Automation

Automate the intake of new print jobs from a customer-facing form into Artworker. POST /v2/job creates the job, follow-on calls to /v2/job-item/{id}/import-files attach the customer-supplied artwork, and /v2/job-item/{id}/request-artwork triggers the request flow when artwork is missing. Saves print operators from re-keying job specs into the Artworker UI.

POST /v2/job to create a job for SKU 'BOX-12', then call /v2/job-item/{id}/import-files to attach the customer-supplied PDF

Packaging Proofing Loop

Run a proofing loop on packaging artwork by creating a workflow task per proof, attaching pages, and using webhooks to know when each task moves between states. The /v1/taskapi/workflows endpoints expose task creation and file/page management; /v1/webhook_endpoint registers the listener.

List workflows, pick the proofing workflow id, attach the new artwork file via /v1/taskapi/workflows/{workflowId}/task/{taskName}/files, and register a webhook for task-state-changed events

Production Status Sync

Sync Artworker production status into an upstream ERP or order system using webhooks plus targeted reads on /v2/job-item/{id}. When a job item is completed, the webhook fires and the receiver can mark the corresponding ERP order line as ready to ship.

Subscribe to job-item completion events via /v1/webhook_endpoint, and on each event fetch /v2/job-item/{id} and update the corresponding ERP order line

Agent-Driven Artwork Request via Jentic

Let an internal AI assistant trigger an artwork request to a supplier when a job item is short on files. The agent searches Jentic for 'request artwork in Artworker', loads the schema for /v2/job-item/{id}/request-artwork, and executes — without managing the API key directly.

Search Jentic for 'request artwork in Artworker', load the schema, and execute against job item id 5012 to issue an artwork request

Key Endpoints

19 endpoints — jentic publishes the only available openapi specification for artworker api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v2/job

Create a new artwork job

GET

/v2/job-item/{id}

Fetch a job item by id

POST

/v2/job-item/{id}/complete

Mark a job item complete

POST

/v2/job-item/{id}/request-artwork

Request artwork from a supplier for a job item

POST

/v2/job-item/{id}/import-files

Import files into a job item

GET

/v1/taskapi/workflows

List task workflows

GET

/v1/taskapi/workflows/{workflowId}/task/{taskName}

Fetch a workflow task

POST

/v1/webhook_endpoint

POST

/v2/job

Create a new artwork job

GET

/v2/job-item/{id}

Fetch a job item by id

POST

/v2/job-item/{id}/complete

Mark a job item complete

POST

/v2/job-item/{id}/request-artwork

Request artwork from a supplier for a job item

POST

/v2/job-item/{id}/import-files

Import files into a job item

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Artworker API keys are stored encrypted in the Jentic vault and applied as the api_key query parameter at execution time, keeping the key out of agent context and log output.

Intent-based discovery

Agents search Jentic with intents like 'create an Artworker job' or 'request artwork in Artworker' and Jentic returns the matching operation with its input schema, so the agent doesn't need to choose between v1 task endpoints and v2 job endpoints by hand.

Time to first call

Direct Artworker integration: 1-2 days to handle v1/v2 path differences, file import payloads, and webhook registration. Through Jentic: under an hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Figma REST API

Figma is where the artwork is designed; Artworker is where it is produced and proofed

Pair when an agent exports artwork from Figma and needs to push it into an Artworker job for production.

Complementary

Slack API

Slack receives the human-facing notifications that an Artworker job has progressed

Use when an Artworker webhook fires and the agent should post a status update into a production Slack channel.

Complementary

HubSpot CRM Deals API

HubSpot tracks the deal that triggers a production job in Artworker

Pair when a closed-won deal in HubSpot should automatically create a corresponding Artworker job for production.

FAQs

Specific to using Artworker API API through Jentic.

Why is there no official OpenAPI spec for Artworker API?

Artworker does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Artworker API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Artworker API use?

Artworker uses an API key passed as the api_key query parameter on each request. Through Jentic, the key is stored encrypted in the vault and appended at execution time, so the agent never sees the raw key.

Can I create a new artwork job programmatically?

Yes. POST /v2/job creates a job, and you can then attach files to its items via /v2/job-item/{id}/import-files or trigger a supplier artwork request via /v2/job-item/{id}/request-artwork.

What are the rate limits for the Artworker API?

Artworker does not publish a hard public rate limit. The API is intended for production-system integration rather than end-user polling, so keep traffic to event-driven calls and webhook-triggered reads.

How do I subscribe to job completion events through Jentic?

Run pip install jentic, then search Jentic with 'register Artworker webhook', load the schema for POST /v1/webhook_endpoint, and execute with your handler URL. Artworker will then push events such as job-item completion to that URL.

Can I attach pages to a workflow task?

Yes. /v1/taskapi/workflows/{workflowId}/task/{taskName}/files and /v1/taskapi/workflows/{workflowId}/task/{taskName}/files/{fileNum}/pages let you attach files and individual pages to a task within a workflow.