Skip to content
TaxComposer

Bookkeeping API and MCP

Safe retries and revisions in a filing API

A network timeout should not create a second return. A stale assistant response should not overwrite a newer correction. Build these two protections into your integration from the start.

By TaxComposer · Updated · 2 min read

Give one logical action one retry identity

Use the operation’s documented idempotency mechanism. Return preparation accepts an Idempotency-Key on REST requests and an idempotency_key argument through the hosted MCP tool. W-9 invitations use request_key; imported W-9 data uses external_id. These are different contracts, not interchangeable field names.

Persist the request identity with the intended action in your own job record. Reuse it for retries of the same action and inspect the returned resource rather than inventing a new key after every timeout.

Source: TaxComposer API Documentation ↗

Bind edits to the version the user reviewed

IRIS draft updates require the exact filing reference, revision and hash, explicit confirmation, targeted changes and an idempotency key. Changes use the documented JSON-pointer paths under the header or records.

A masked response is not a replacement payload. Preserve private values on the server and submit only the confirmed field changes. If a revision conflict occurs, reload the current draft and ask the user to review the difference.

Source: TaxComposer MCP connections ↗

Rerun checks after changes

A validation result belongs to the exact draft it checked. Fetch the current workflow after an edit and rerun the installed validation. Keep source findings and unresolved IRS rules visible rather than treating “request succeeded” as “return accepted.”

MeF uses its own draft and mapping hashes with targeted field changes. Do not transplant an IRIS payload or revision contract into a MeF request.

Source: TaxComposer API Documentation ↗

Reconcile before retrying an uncertain action

For a timeout or interrupted connection, read the saved resource or request status before submitting again. Preserve the returned request ID, resource ID and retryable status in operational logs without storing taxpayer payloads.

A future production acknowledgment must be tracked separately from draft saves, payment receipts and simulated results. Retries should resume the known workflow state, not advance it based on an assumption.

Source: TaxComposer developer workflow guide ↗

Primary sources

Sources checked November 12, 2026. Use the instructions for your reporting year and circumstances.

Your next step

Connect your bookkeeping workflow.

Use the current API contract and discover the tools available to your MCP connection.

API Documentation →Connect with MCP →

TaxComposer is production-ready for IRS IRIS e-filing. Prepare for free and pay $1 per form when you file.