Architecture Principle · 02 of 9
API-First
If a feature exists in the UI, it exists in the API. External integrations are not afterthoughts — they use the same interfaces internal modules use.
What this means
In practice.
Every action available in the UI is also available as an API call
External systems (SAP, Salesforce, custom apps) integrate as first-class consumers
Internal modules cannot bypass the API — no hidden coupling, no shortcuts
OpenAPI 3.0 specs published for every endpoint; auto-generated SDKs available
How it works
Under the hood.
Contract-first
Every endpoint defined in OpenAPI spec before implementation. Spec is the source of truth.
Versioned
Breaking changes require new API version. Old versions deprecated with 12-month notice.
Auth + RBAC
Every API call goes through authentication + permission check. No internal back-doors.
Webhooks
Outbound webhooks for state changes — order created, invoice paid, batch produced. Subscribers configure their own listeners.
Visual
Real-World Example
Real-world: SAP integration in 5 days
Before
Customer wanted to push approved POs from SAP into Papyrus for execution.
After
Used the standard POST /procurement/purchase-orders endpoint. SAP connector configured in 3 days, tested in 1, live in 5. Zero custom code on Papyrus side.
Ready to modernize your mill?
See Papyrus BPApp
in your mill.
Book a personalized demo. We'll walk through every module relevant to your operation — from Deckle optimization to GSTR-3B compliance.