FreeAgent API vs Merge Accounting 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.

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.

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

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