Your systems already hold the data. T‑API turns it into signed contracts — in a single call.
Transaction API is an interface for the automatic production of documents from the data already living in your ERP, HRIS or CRM. One call → a complete set of 8+ documents generated, signed with a qualified e‑signature and filed into an audit‑ready archive.
{ "event": "employee.onboarding", "source": "enova365", "candidate": { "name": "Anna Kowalska", "pesel": "85091548926", "role": "Logistics Specialist" }, "contract": { "type": "employment", "start": "2026-06-01", "salary": 8400 }, "package": "hr.full" // 8 docs }
A specific operational problem. Not everyone needs it — where it's needed, it's irreplaceable.
Transaction API makes sense where volume, a source system and compliance meet in a single process. Four situations in which it usually comes up in conversation.
Companies with high volumes of recurring documents
400+ hires/month, mass amendments, attachment bundles, protocols, offers. Where scale hits first and you can see it on the HR team's calendar.
Organizations with an existing HRIS / ERP / CRM
Where data is the source of truth and never goes back to manual re-entry. Workday, SAP, enova365 and Teta HR stay in place — Pergamin sits alongside them.
IT teams with architectural discipline
Who choose a documented API over an integration agreed "over a call". Sandbox, versioning, zero impact on existing systems.
Operations teams under labour-inspection pressure
Where the audit trail and a complete package are a hard requirement, not a nice-to-have. From 8 July 2026, every gap compounds into a double penalty.
From the data in your system to a signed set in the archive — four steps.
The classic approach: HR logs into the HR system, exports the data, copies it into Word, sends it by courier, waits for a signature, scans it, uploads it to the e-file. Transaction API closes that entire loop — no user login, no copy-paste.
A call from your system
A single webhook or REST call with a payload — candidate data, contract parameters, the list of required documents. No volume limits within a single transaction.
POST /api/v2/transactionsPackage generation
Pergamin produces a complete set of documents from controlled templates (contract, GDPR, declarations, attachments). Each one versioned and compliant with Polish labour law.
templates · v2 · PL labour lawSigning path
Qualified e-signature (QES, art. 25 eIDAS) — mobile-first, 5 languages (PL/EN/UA/ES/VI), a mixed path for employees without email/smartphone and for foreign nationals.
QES eIDAS · 5 languagesArchive with an audit trail
Every document searchable, versioned, with a full action log. A complete employee file available in 2 minutes, not 2 weeks. Data in AWS Frankfurt (EU-Central-1).
audit trail · sha-256 · EUWhat Transaction API is — and what it isn't.
Pergamin doesn't replace your HRIS or ERP. It works alongside as an execution layer that closes the document loop from data to a signed archive.
An execution layer for document production.
- A worker that produces documents from your data.
- A closed loop: data → document → signature → archive.
- An interface for scaling without a proportional rise in HR costs.
A replacement for your HR system — it works alongside it.
- A replacement for Workday, SAP, enova365 or Teta HR — it works alongside them.
- A signing-only tool — it closes the entire document loop.
- A payroll system — it doesn't calculate pay.
- An e-file — it delivers the file as the output of the process.
The same documents, different process economics.
A comparison of the manual path (HR logs into the system, exports, copies, sends, scans) with Transaction API (one call → audit-ready archive).
Security your IT team will approve.
Your data stays in the EU — hosting in AWS Frankfurt and end‑to‑end encryption. ISO 27001, eIDAS and GDPR certifications are audit‑ready, and the documented API — with its sandbox and connectors — deploys without regression risk to your existing systems.
Checklist for your IT team
No system replacement. No regression risk.
Standard enterprise in 4–6 weeks. Scenarios with a ready connector and webhooks go live in 1 day. 150 companies have used Pergamin since 2017.
No-code integrations
For scenarios where your system has webhooks or a ready connector — enova365, Teta HR, SAP, Workday. Configuration instead of code.
Typical enterprise
Full integration with HRIS/ERP, template mapping, tests with your data, production go-live. No replacement of existing systems.
Have used Pergamin since 2017
From SMBs to regulated enterprises in Poland. Logistics, retail, finance, pharma, automotive — wherever volume meets compliance.
Workday, SAP, enova365, Teta HR stay in place. Pergamin steps in alongside as the execution layer.
We don't replace your HR system. We take the data that's already in it and return a finished, signed set of documents — no logins, no copy‑paste, no manual bundles.