Verify the configured iCount API token works by fetching basic app/account info.

Create a document (invoice, receipt, order, offer, etc.) in iCount. Prefer non-tax types (order/offer) for testing since iCount has no hard delete, only cancel. Real tax documents (receipt/invrec) require a payment breakdown or iCount will reject them.

Search existing iCount documents by type, status, client, date range, or document number. At least one filter is required. A search that matches nothing returns { docs: [], matched: 0 } — that is a normal empty result, not an error. A very broad date range can be rejected as too_many_results; narrow it rather than raising maxResults, which does not lift that limit.

Fetch full details of a single existing document by type and number.

Cancel an existing document (iCount has no hard delete — this is the only way to void one). Irreversible: confirm the document number with the user before calling.

Mark a document as closed/paid, optionally linking it to base documents it settles.

Convert a document to another type (e.g. offer -> order). Omit conversionType to first list the valid conversion options for this document; pass one of those values back in conversionType to perform the actual conversion.

Get a viewable/printable URL (PDF) for an existing document.

Create a new client/recipient record directly, without also creating a document.

Update fields on an existing client. Only fields provided are changed.

Fetch full details of a single client by id.

List clients in the account. Returns { total, returned, clients } so you can tell when the list was truncated.

Permanently delete a client record. Unlike documents, this is a real, irreversible delete — confirm with the user first, and prefer it only for clients with no associated documents.

List one client's open (unpaid/unsettled) documents — their outstanding balance. Requires a client: pass clientId (preferred), email, or clientName. There is no all-clients mode; for that, use icount_search_documents with status 0.