Invoice Ninja

Getting a token

1. Sign in and open Settings → Account Management → API Tokens (on v5; on a self-hosted instance the same page exists).
2. Create a token and put it in INVOICENINJA_API_TOKEN.
3. Set INVOICENINJA_URL. For the hosted service that is https://invoicing.co; for a self-hosted instance, your own root. No trailing slash and no /api/v1 — the adapter appends it.

The header is X-API-TOKEN.

One token, one company. Invoice Ninja supports several companies per account, and the token is bound to the one it was created in. A second company needs a second token and a second connector.

include resolves relationships in one call: include=client,invitations on an invoice, include=contacts on a client. Without it you get ids and have to fetch each one.

Status is a small integer, and each document type numbers it differently. For invoices: 1 draft, 2 sent, 3 partial, 4 paid, 5 cancelled, -1 reversed. For quotes: 1 draft, 2 sent, 3 approved, 4 converted, 5 expired. Do not assume they line up.

Amounts are floats in the client's currency, and balance is what is still owed while amount is the invoice total. A receivables figure wants balance.

Soft deletes are hidden by default. Archived and deleted records are excluded unless you ask for them, which is usually right — but it is why a record somebody swears exists can be missing.

Self-hosted, which is the thing to plan for.

• On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
• On an internal host (invoices.intern, 10.0.0.x), self-host AnythingMCP on the same network and add that host to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.