Skip to content

Noja Partner API

Create clients, push receivable and payable invoices, and request financing on any of them — from inside your own product. Onboarding runs either through your screens or through a white-labelled flow we host.
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

You hold the invoice. Noja decides what it is worth today. This API is the seam between those two facts — and nothing in it asks you to change how invoices are created, sent, or stored.

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 invoices. Receivables and payables, both directions, one endpoint. Invoices sent purely as trading history build the payment-behaviour record that produces a credit limit; invoices flagged for financing get scored and decided.
  • Get told what changed. Webhooks push limit changes, financing decisions, settlements, and onboarding completion back to you.

Invoices come to 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.

The rule worth reading twice

You own invoice facts. Noja owns financing verdicts.

You write amounts, dates, counterparties, and payment outcomes. We write credit limits, financing decisions, and risk state. The only status you ever change is the payment status of a historical invoice — and even that is optional.

Every endpoint in this reference carries a marker showing which side owns it.

How a client moves through the system

  1. Create the client from their company registration number. It becomes a prospect immediately.
  2. Send trading history — twelve months if you have it, three at minimum. This is what produces a credit limit.
  3. Onboard them, either through your screens or through the hosted flow.
  4. Underwriting approves, a limit and pricing are assigned, and you receive a webhook.
  5. Flag invoices for financing as they age past term.

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.

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 that handles history, payables, and financing.