Invoice Ninja API vs Xero API + MCP

Invoice Ninja API

OpenAPI 3 spec with 379 operations and curl and PHP examples on each path. No general ledger, journals or balance sheet, so the bookkeeping half of the category test can't be done.

Xero API + MCP

Granular OAuth scopes, such as accounting.reports.profitandloss.read, required for apps created from 29 April 2026. Developer docs, including the per-minute rate limits, only render with JavaScript.

Invoice Ninja API

1. Send X-Requested-With: XMLHttpRequest with X-API-TOKEN on every call
2. Prototype against demo.invoiceninja.com with X-API-TOKEN: TOKEN before asking for real credentials
3. Add ?mark_sent=true to the save to make an invoice live, or ?send_email=true to send it. A plain create is a draft
4. Stay under 1,000 requests a minute per token on the hosted service and 20 a minute on report exports
5. Record a supplier bill as an expense or purchase order. There's no bills resource

Xero API + MCP

1. Send xero-tenant-id on every call. The token alone doesn't name the organisation
2. A bill is an Invoice with Type ACCPAY, a sales invoice is ACCREC. There's no separate bills endpoint
3. Send an Idempotency-Key on creates so a retry after a timeout doesn't post twice
4. Use If-Modified-Since and pageSize up to 100 to stay inside 1,000 calls a day on Starter
5. Set XERO_SCOPES to read scopes only when the agent shouldn't write. The MCP still lists its write and delete tools