FreeAgent API vs Invoice Ninja API

FreeAgent API

Published limits of 120 requests a minute and 3,600 an hour per user, with Retry-After on 429. No OAuth scopes, so a token can do anything the authorising user can.

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.

FreeAgent API

1. Store the new refresh token from every refresh response. The old one stops working
2. Create the invoice, then PUT /v2/invoices/:id/transitions/mark_as_sent. A draft isn't visible to the customer
3. Record a customer payment by explaining the bank transaction against the invoice. There's no invoice payments endpoint
4. Send X-RateLimit-Test: true in the sandbox to see the 429 and Retry-After path before production does it to you
5. Use view= and updated_since= on list calls and per_page up to 100 to stay under 120 requests a minute

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