Codat vs Rutter Accounting API

Codat

Public OpenAPI specs, an Idempotency-Key header on writes, Retry-After on 429 and a written three-month deprecation notice suit an agent that retries. Access is the limitation. No price or self-serve signup is published, the general Accounting API is closed to new clients, and API keys carry no scopes.

Rutter Accounting API

Idempotency-Key header on writes, and prefer_sync writes that fall back to async after 30 seconds. Production prices are quote-only.

Codat

1. Send Authorization: Basic <base64 of the API key> to https://api.codat.io. The Portal shows the ready-made header value
2. Send a new GUID as Idempotency-Key on every POST and PATCH, and reuse the same key when retrying after a 429
3. Treat writes as asynchronous on most APIs. Keep the push operation key and wait for the {dataType}.write.successful or .unsuccessful webhook
4. Call the Get model (options) endpoint for the connection before a create or update, because required fields differ by accounting package
5. Filter with query=modifiedDate>... and keep pageSize at 100. The daily quota is 1,000 requests times one plus the number of active connected companies

Rutter Accounting API

1. Send X-Rutter-Version: 2024-08-31 on every call
2. Send an Idempotency-Key on every create so a retry after a timeout doesn't write twice
3. Use response_mode=prefer_sync and handle the 202 async_response anyway
4. Treat 452 as the ledger throttling you and 429 as Rutter's 500-per-10-seconds organisation limit
5. Keep access_token out of logged URLs. The docs only show it as a query parameter