Check code against live templates
Connect
SPIRITT
PDF-API.ioPDF-API.io.
Templates under control.
SPIRITT reads your PDF-API.io template library and keeps everything around it in order: catalogs, code references, release checks and the systems that pick the right template for every document.
What you can do with PDF-API.io.
One source of truth
Every template and ID cataloged where developers and ops can find it.
Code and templates aligned
References in your repos are checked against the templates that actually exist.
Changes never surprise you
New and removed templates are caught and announced the day they happen.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your product or document operations team.
02
Connect PDF-API.io
Connect PDF-API.io so SPIRITT can read your template library.
03
Name the outcome
Ask for a catalog, an audit or a sync. SPIRITT builds it and keeps it current.
Hand over a mission.
Choose a mission. Make it yours.
Put PDF-API.io to work.
Keep every template accounted for
Questions
PDF-API.io, with SPIRITT.
01What does SPIRITT do with PDF-API.io?+
It reads your template library and builds catalogs, code audits, release checks and syncs around it.
02Can it check our code?+
Yes. SPIRITT reads your GitHub repos, finds template references and verifies each one against the live library.
03How does it spot changes?+
It keeps the previous template list and compares each run, so additions and removals are caught the same day.
04Where can template data go?+
Notion, Confluence, Supabase, Google Sheets, HubSpot, Slack or any connected app that needs current template IDs.
05Can it gate releases on template IDs?+
Yes. SPIRITT checks every template ID in a release pull request against the live library and comments the result before merge.
06How do I get started?+
Open a SPIRITT workspace, connect PDF-API.io and ask for the catalog or audit you need.