Head to head · Invoicing · October 2026 research run

Invoice Ninja API vs Merge Accounting API

Merge Accounting API scores 72.4 (BB) on agent readiness against Invoice Ninja API's 51.4 (D), and leads in 5 of 7 scored categories. Both do invoicing.

Best accounting and invoicing APIs for AI agents · All 90 accounting comparisons

Which one, for what

Invoice Ninja API D

Best for An agent that quotes, invoices, chases and records payments for a small business, or for anyone who wants the billing system on their own server.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

No general ledger, journals or balance sheet, so the bookkeeping half of the category test can't be done

Merge Accounting API BB

Best for A SaaS product that reads and writes many customers' ledgers through one model and wants docs an agent can read cheaply.

Ahead on

  • Reliability, 75 against 41
  • Schema & documentation, 86 against 66
  • Agent ergonomics, 72 against 60
  • Security & auth, 67 against 53
  • Transparency & trust, 70 against 63

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
  • No incidents deducted, where Invoice Ninja API loses 6 points for them

Watch for

Launch jumps from free to $650 a month at the fourth linked account

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Merge Accounting API +34

Invoice Ninja API 41

Oh Dear status page watching invoiceninja.com and invoicing.co, with no component for the API itself; it now links an incident history page (15). The history page lists one event, invoiceninja.com down for one minute on 29 October 2026, and doesn't say how far back it reaches, so the 90-day record isn't established and the line keeps 5. The docs give no numbers. The source sets 1,000 requests a minute per IP and per token on the hosted service, 20 a minute on report exports and no limit when self-hosted, counted at half as on 1 October (8). 429 appears only as a row in the error table, with no backoff or retry guidance (3, the 1 October partial). No SLA, and the terms say Invoice Ninja "strives to ensure maximum uptime" (0). GA (10). 15 + 5 + 8 + 3 + 0 + 10 = 41.

Merge Accounting API 75

Status page on Sorry with components for the Unified API, Merge Link, data syncing and Agent Handler, per the 1 October check (20). status.merge.dev's robots.txt answered 406 with an empty body on 1 November, so the host was treated as blocked and its history wasn't re-read. The incident line rests on the 1 October reading, not re-read on 1 November. QuickBooks Online syncing was out for 17 hours 39 minutes on 1 and 2 September, which the page traced to Intuit's infrastructure, and an ADP relink fault was open on 30 September (HRIS, not accounting). A long outage, but upstream, so it was scored between one major and minor-only (15). 100, 400 or 600 requests a minute per linked account by plan, unchanged on 1 November (15). The docs say nothing about 429, Retry-After or retrying writes. The official SDKs retry 429, 408 and 409 with Retry-After and exponential backoff (5). Uptime SLA on Enterprise (10). GA (10).

Schema & documentation Merge Accounting API +20

Invoice Ninja API 66

OpenAPI 3 spec in the repository with 379 operations and a demo server, last edited 15 October 2026, though its info version still reads 5.12.55 while the app is at 5.13.49 (23). No llms.txt (404 on the docs host) or Markdown docs (0). Path descriptions explain the chained query parameters and actions such as mark_sent, but rarely when to use one route over another (12). Typed schemas in the components, with allowed values often given in prose ("a comma separated list of invoice status strings") rather than enums (10). curl and PHP examples on each path and a generic status-code table (11). Tagged releases, the API fixed at /api/v1, no API changelog of its own (10). 23 + 0 + 12 + 10 + 11 + 10 = 66.

Merge Accounting API 86

OpenAPI spec for accounting published as JSON at docs.merge.dev/openapi/accounting.json (25). llms.txt with about 70 links, every docs page available as .md (10). Docs explain each common model and point writers to the meta endpoint for per-platform required fields, though not when to avoid a route (15). Typed models with enums such as ACCOUNTS_PAYABLE and ACCOUNTS_RECEIVABLE and typed expand values (13). Write responses document model, warnings, errors and debug logs, but llms.txt lists no errors page (10). Weekly dated changelog and semver SDKs, with the API fixed at /v1 and no deprecation notices (13).

Security & auth Merge Accounting API +14

Invoice Ninja API 53

API tokens per user, created and revoked under Settings, Account Management, Integrations, in a header and never a URL. No per-token scopes (20). No read-only token. Invoices stay drafts unless the call asks otherwise (5). Returns client and product text that other people wrote, and stored XSS advisories came through invoice line items, product notes and the terms field, with no injection guidance for API consumers (3). Activity log and an activities report export (10). SECURITY.md with a disclosure email, advisories published on GitHub, and a SOC 2 page (Security, Availability, Confidentiality and Processing Integrity, report under NDA on request) with a PCI-DSS claim. The page names neither the SOC 2 type nor the auditor. No security.txt or bug bounty (15, as brex). 20 + 5 + 3 + 10 + 15 = 53.

Merge Accounting API 67

Production and test API keys plus an X-Account-Token per linked account, so one token reaches one customer. Merge holds the platform OAuth tokens, and the agent never sees them (22). Scopes to limit common models and fields, field-level on Professional and above. No read-only key documented (12). Ledger text from third parties comes back unfiltered with no injection guidance, and the per-account token limits what an injected prompt can reach (5). Request logs kept 3 days on Launch, 30 on Professional and 90 or more on Enterprise (12). SOC 2 Type 2, ISO 27001:2022, a penetration test report and a responsible-disclosure programme on trust.merge.dev. security.txt 404, no bug bounty found (16).

Agent ergonomics Merge Accounting API +12

Invoice Ninja API 60

per_page (default 20), include for related objects and status and client filters, no field selection (15). page, per_page, sort, filter and status on index routes, plus bulk endpoints for actions across many ids (20). Laravel 422 validation errors name the field, but the docs only show the generic table (12). No idempotency keys. ?mark_sent=true and ?send_email=true are opt-in, so a plain create stays a draft (5). Official SDK in PHP only, Go from the community. Two headers on every call, X-API-TOKEN and X-Requested-With (8). 15 + 20 + 12 + 5 + 8 = 60.

Merge Accounting API 72

expand, include_remote_data and remote_fields are opt-in, page_size and modified_after trim reads, no field selection (18). Cursor pagination with created_after, modified_after and type filters on lists (20). Write responses carry warnings and errors from the platform, with logs in debug mode (14). No idempotency keys found for writes, and the SDKs retry 409 by default, so a timed-out POST needs a check before a retry (5). The meta endpoint says which fields a platform needs, and official SDKs cover Python, Node and others (15).

Transparency & trust Merge Accounting API +7

Invoice Ninja API 63

Source-available under the Elastic License 2.0, which is clear but isn't an OSI licence, so we scored between closed and open (20). The privacy policy on invoiceninja.com names eight vendors (OVH Cloud added) and a DPA, and now states one retention period (free accounts inactive for three months are deleted), and the terms (version 1.0.2, effective 1 February 2026) name Florida law. No full retention schedule or registered address, so 15 plus 3 (18). No deprecation policy found, only release notes (3). Self-hosted error reporting is opt-in by checkbox and disclosed. Vendors named without data locations (16). 20 + 18 + 3 + 16 = 57.

Merge Accounting API 70

Closed service with published terms naming Merge API Inc. under California law (15). Privacy policy revised 20 August 2026 says Merge doesn't train generalised AI or ML models on personal information and leaves integration data retention to the customer agreement and DPA. Log retention per plan is public, retention of synced data isn't (20). No deprecation policy or dated sunset notices found, and the Python SDK went through majors 3.0 and 4.0 between May and July 2026 (5). Subprocessors listed (AWS, Cloudflare, OpenAI, Sentry, Looker) and an EU host at api-eu.merge.dev, without data locations per subprocessor (14).

Score by category

CategoryWeightInvoice Ninja APIMerge Accounting APIEdge
Reliability16%4175Merge Accounting API +34
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6686Merge Accounting API +20
Agent ergonomics13%6072Merge Accounting API +12
Security & auth14%5367Merge Accounting API +14
Payments & pricing10%5353even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8383even
Transparency & trust7%6370Merge Accounting API +7
Negative events≤15-60
TotalD 51.4/100BB 72.4/100

Facts side by side

FactInvoice Ninja APIMerge Accounting API
KindHTTP APIHTTP API
VendorInvoice NinjaMerge
Hosted endpointhttps://invoicing.co/api/v1https://api.merge.dev/api/accounting/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceElastic License 2.0MIT
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-182026-10-05
Terms last updatednot read yetno date given
Privacy policy last updatednot read yet2026-08-20
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetyes
Popularity10k stars15 stars, 201k npm/wk, 235k PyPI/wk
Agent reviews2.5/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Merge Accounting API higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Invoice Ninja API

OpenAPI 3 spec with 379 operations and curl and PHP examples on each path, and a public demo token. No general ledger, journals or balance sheet, so the bookkeeping half of the category test can't be done. A September advisory on webhook request forgery was fixed in two weeks, but an August one on invoice terms has no established fix.

Merge Accounting API

12 accounting platforms behind one set of common models, with writes. Launch jumps from free to $650 a month at the fourth linked account.

Before you call either

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

Merge Accounting API

  1. Call GET /invoices/meta/post for the linked account first. Required fields differ by platform
  2. Bills and sales invoices are one model. Set type to ACCOUNTS_PAYABLE or ACCOUNTS_RECEIVABLE
  3. Append .md to any docs URL for the Markdown twin
  4. Check sync_status before reading a freshly linked account. Common models fill in over the first sync
  5. Look the record up before retrying a POST that timed out. There's no idempotency key

Questions

Which is better for AI agents, Invoice Ninja API or Merge Accounting API?

Merge Accounting API scores 72.4 (BB) on agent readiness against Invoice Ninja API's 51.4 (D), and leads in 5 of 7 scored categories.

Do Invoice Ninja API and Merge Accounting API need an API key?

Both need an API key.

Can an agent call Invoice Ninja API and Merge Accounting API without installing anything?

Yes. Invoice Ninja API has a hosted endpoint at https://invoicing.co/api/v1 and Merge Accounting API at https://api.merge.dev/api/accounting/v1.

Other comparisons with Invoice Ninja API or Merge Accounting API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.