Integrations Overview
Connect LintPDF to prepress workflow engines, print ERP/MIS systems, and no-code automation platforms.
Integrations Overview
LintPDF is a REST API. Any system that can make HTTP calls can integrate with it. This section covers documented integration paths for common print industry systems.
Bringing Your Own Preflight
Many of the systems below — Enfocus Switch, Esko Automation Engine, Hybrid CLOUDFLOW — already run preflight upstream (PitStop, callas, or custom rules). Rather than double-processing, submit the PDF alongside the upstream report in external import mode:
curl -X POST https://api.lintpdf.com/api/v1/jobs \
-H "Authorization: Bearer lpdf_live_..." \
-F file=@artwork.pdf \
-F external_report=@pitstop-report.xml \
-F preflight_source=external
LintPDF parses the findings, renders them in the viewer, mints share links, and powers approval verdicts — without re-checking the PDF. See External Preflight Imports for the full format matrix and Custom Import Mappings if your internal report shape isn’t built in.
Integration Approaches
Direct API Integration
Your system calls LintPDF directly:
POST /api/v1/jobswith a PDF file and a profile ID- Poll
GET /api/v1/jobs/{job_id}until status iscompleteorfailed - Read findings from the response
This works for any system with HTTP client capabilities — ERP/MIS platforms, custom scripts, no-code tools.
Indirect Integration (via Workflow Engine)
Your ERP sends jobs to a prepress workflow engine (Enfocus Switch, Esko Automation Engine, Hybrid CLOUDFLOW), which calls LintPDF as a preflight step:
- ERP sends JDF + files to the workflow engine
- Workflow engine submits the PDF to LintPDF
- LintPDF returns findings
- Workflow engine routes pass/fail and reports back to the ERP
Webhook-Driven Integration
Instead of polling, register a webhook endpoint to receive results automatically:
curl -X POST https://api.lintpdf.com/api/v1/webhooks \
-H "Authorization: Bearer lpdf_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"url": "https://your-system.com/lintpdf-webhook",
"events": ["job.completed", "job.failed"]
}'
LintPDF sends a POST to your URL when the job finishes. The payload includes the full job result with findings and summary.
Quick Reference
The core submit-and-check flow in any integration:
# 1. Submit a PDF
curl -X POST https://api.lintpdf.com/api/v1/jobs \
-H "Authorization: Bearer lpdf_your_api_key" \
-F file=@artwork.pdf \
-F profile_id=gwg-sheetfed
# Response: { "id": "job_abc123", "status": "pending" }
# 2. Poll for results
curl https://api.lintpdf.com/api/v1/jobs/job_abc123 \
-H "Authorization: Bearer lpdf_your_api_key"
# Response when complete:
# {
# "status": "complete",
# "summary": {
# "passed": false,
# "error_count": 2,
# "warning_count": 1,
# "advisory_count": 3
# },
# "findings": [...]
# }
Severity levels:
| Severity | Meaning |
|---|---|
error | Critical — file will cause production issues |
warning | Warning — should be reviewed before production |
advisory | Informational — no action required |
A job passes when error_count is 0.
Integration Guides
Prepress Workflow Engines
| System | Integration Type | Guide |
|---|---|---|
| Enfocus Switch | HTTP Request element or Scripter | Enfocus Switch |
| Esko Automation Engine | Interact with Web Service task | Esko AE |
| Hybrid CLOUDFLOW | REST API / custom workflow node | Hybrid CLOUDFLOW |
Print ERP / MIS
| System | Integration Type | Guide |
|---|---|---|
| Label Traxx | Direct (Cloud API) or indirect (AE/CLOUDFLOW) | Label Traxx |
| CERM | Indirect (JDF via AE/CLOUDFLOW) | CERM |
| EFI Pace | Direct (API) or indirect (JDF/Fiery) | EFI Pace |
| Tharstern | Indirect (AE) or direct (web services) | Tharstern |
| PrintVis | Direct (D365 APIs / Power Automate) | PrintVis |
| Radius | Indirect (JDF via AE/CLOUDFLOW) or middleware | Radius |
| NetSuite | Direct (SuiteScript Restlets) or middleware | NetSuite |
Desktop & Automation Tools
| System | Integration Type | Guide |
|---|---|---|
| Desktop App | Native GUI hot folder manager (macOS, Windows, Linux) | Desktop App |
| Hot Folder CLI | Python CLI directory watcher for servers | Hot Folder |
| Zapier / Make / n8n | Webhook + HTTP modules | Zapier, Make & n8n |
Authentication
All integrations use the same auth method:
Authorization: Bearer lpdf_your_api_key
Generate your API key in the LintPDF dashboard. See Authentication for details.