FreshBooks API vs QuickBooks Online API + MCP

FreshBooks API

OAuth scopes split read and write per resource, such as user:invoices:read. Rate limits have no numbers, status code or headers.

QuickBooks Online API + MCP

Official MCP server from Intuit with 145 tools and flags to remove write, update or delete tools. Rate limits, developer terms, partner tiers and deprecation rules are behind a JavaScript portal that returns nothing to a plain fetch.

FreshBooks API

1. Call /auth/api/v1/users/me first and keep both ids. Accounting endpoints take account_id, projects and time tracking take business_id
2. Serialise token refreshes. Issuing a new refresh token kills the old one at once
3. Mark an invoice as sent (action_mark_as_sent) or email it. Reports ignore drafts
4. Send x-api-version: 2023-09-25 on journal entry calls
5. Back off on any throttling response yourself. There's no Retry-After to read and no published limit

QuickBooks Online API + MCP

1. Store the realmId with the tokens. Every URL needs it and the token alone doesn't name the company
2. Persist the new refresh token from every refresh response. The previous one expires 24 hours later
3. Use the query endpoint with MAXRESULTS and STARTPOSITION for reads rather than fetching by id
4. Send a unique requestid query parameter on writes, so a retry returns the first response instead of posting twice
5. On 429, wait for Retry-After before retrying, and don't retry other 4xx errors