Authenticate
Server-side API access with clear permissions per workspace.
Finance workflows through an API
Connect Norman to internal tools, customer portals, or production workflows so finance data is not copied manually.
For integrated finance operations
One API for operational finance data instead of separate exports for every process.
Invoices
Create, read, update, and sync with payment status.
Receipts
Receipts, attachments, OCR fields, and transaction matching.
Transactions
Bank activity and bookkeeping state for internal workflows.
Tax status
VAT, EÜR, and annual workflow status for operational surfaces.
Access and webhooks
Server-side scopes, webhooks, and workspace permissions keep integrations controlled.
What a clean API removes
Programmatic finance data replaces month-end exports and manual handoffs.
CSV exports
at month-end
Manual sync
between spreadsheets and internal tools
Custom logic
for finance data in every product
What integration looks like
Sync data
Invoices, receipts, transactions, and status data connect through stable resources.
Trigger workflows
Create invoices, check open issues, or sync finance state into your product.
Build Norman into your workflow
Start for free and connect your finance operations to the Norman API.
Start for freeFAQ
Is the Norman API meant for public apps?
It is designed for server-side integrations, internal tools, platforms, and product-adjacent finance workflows.
What data can I connect?
The focus is invoices, receipts, transactions, matches, and accounting or tax workflow status.
How do permissions work?
API access is server-side and scope-based. Integrations receive only the permissions needed for the specific workspace and use case.
Can the API submit tax filings?
No. The API can provide structured finance and status data. Tax submissions remain a controlled Norman workflow.