Invoice Ninja
Invoice Ninja is an open-source invoicing, billing, payments, and expense tracking platform for freelancers and small businesses, available both as a self-hosted application and a managed SaaS at invoicing.co. The Invoice Ninja v5 REST API exposes full CRUD access to clients, invoices, quotes, payments, products, recurring invoices, expenses, projects, and tasks, authenticated with an API token (plus an optional secret) passed via HTTP headers.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Invoice Ninja the way a machine reads it — 14 machine-readable artifacts across 10 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Invoice Ninja scores 29.5/100 (emerging), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Invoice Ninja
Each block below is one kind of artifact we hold for Invoice Ninja. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 10
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Invoice Ninja Activities API
The Activities API from Invoice Ninja — 3 operation(s) for activities.
Invoice Ninja Authentication API
The Authentication API from Invoice Ninja — 2 operation(s) for authentication.
Invoice Ninja Bank Integrations API
The Bank Integrations API from Invoice Ninja — 3 operation(s) for bank integrations.
Invoice Ninja Bank Transaction Rules API
The Bank Transaction Rules API from Invoice Ninja — 2 operation(s) for bank transaction rules.
Invoice Ninja Bank Transactions API
The Bank Transactions API from Invoice Ninja — 3 operation(s) for bank transactions.
Invoice Ninja Charts API
The Charts API from Invoice Ninja — 4 operation(s) for charts.
Invoice Ninja Client Gateway Tokens API
The Client Gateway Tokens API from Invoice Ninja — 2 operation(s) for client gateway tokens.
Invoice Ninja Companies API
The Companies API from Invoice Ninja — 4 operation(s) for companies.
Invoice Ninja Company Gateways API
The Company Gateways API from Invoice Ninja — 2 operation(s) for company gateways.
Invoice Ninja Settings API
The Settings API from Invoice Ninja — 1 operation(s) for settings.
Scroll within the panel for all 10 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Invoice Ninja v5 API
OPEN COLLECTIONSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Invoice Ninja — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/invoice-ninja · machine-readable index on apis.io