Noja Partner API¶
Route a client's whole invoice book to Noja, request financing on the invoices they want advanced, and let the rest stand as collateral — from inside your own product.
| Base URL | https://api.noja.fi/partner/v1 |
| Sandbox | https://api.sandbox.noja.fi/partner/v1 |
| Authentication | OAuth 2.0 client credentials |
| Version | v1 |
What this API does¶
Noja advances money against a client's receivables. The book those receivables sit in is the collateral, so this API is built around getting all of it — not just the invoices someone wants cash for today.
There are three things you can do:
- Register a client. One of your users becomes a Noja prospect from their registration number, a name, and a contact. One call.
- Send every invoice. Receivable and payable, as they are issued. Noja assesses the receivables against the client's facility and decides which to advance against — there is no per-invoice request for you to make.
- Get told what changed. Webhooks push limit changes, financing decisions, settlements, and onboarding completion back to you.
Invoices reach Noja directly from your platform. No e-invoicing network sits in the path, and there is no per-company authorisation flow to run against a third party. Nothing here changes how your users write or send their invoices — only that a copy of every one reaches Noja.
Whole turnover — the rule that shapes everything else
Noja finances against a client's entire receivables book, not against invoices one at a time. The credit limit, the debtor spread behind it, and the recovery of any shortfall are all computed across everything that client trades.
So every invoice must reach Noja — receivable and payable, financed or not. And the client does not choose which ones are financed: they agree an advance rate with Noja once, and it applies to every invoice unless that invoice asks for a different share. Noja decides, invoice by invoice, what it will advance against.
A client can have one invoice withheld by exception. They cannot cherry-pick, and the API is shaped to make that the awkward path rather than the obvious one.
An incomplete book does not make Noja cautious. It makes Noja wrong, quietly: every limit, exposure and payment-behaviour figure is computed on the assumption that it can see everything.
Who owns what
You own invoice facts — amounts, dates, counterparties, payment outcomes. Noja owns financing verdicts — credit limits, decisions, risk state.
Every endpoint in this reference carries a marker showing which side owns it.
How a client moves through the system¶
- Create the client from their company registration number. It becomes a prospect immediately.
- Backfill the book — twelve months of invoices if you have them, three at minimum. This is what produces a credit limit.
- Onboard them, either through your screens or through the hosted flow.
- Underwriting approves, a limit and pricing are assigned, and you receive a webhook.
- Keep sending every invoice as it is issued. Noja assesses each receivable against the facility; you receive a decision per invoice.
Steps 2 and 3 are independent. Invoices are accepted from the moment a client exists — there is no need to wait for approval, and nothing has to be resubmitted once approval lands.
Step 5 is the steady state, and it does not stop. The book has to stay current, not just start complete.
Where to start¶
- Getting started — authentication and your first two calls.
- Core concepts — the five conventions that hold across every endpoint.
- Invoices — the single endpoint every invoice goes through.
- Financing flow — how a decision is reached, and why one batch returns several answers.