List the Manager businesses this connection can reach, with their ids. Every other tool takes an optional 'business' argument; it can be left out when only one business is configured.

Open the local permissions control panel in the browser and return its URL. That panel is where the user ticks which resources this connection may read, create, update or delete, and where businesses and their access tokens are added. Changes apply immediately, no restart.

Browse the resource catalog of a business: every document, list, report and setting the Manager instance exposes, with the operations allowed by the current tick boxes. Start here when you do not know a resource name. Filter with 'search' (e.g. 'invoice', 'tax') or 'group'.

Show what this connection is currently allowed to do for a business: the totals per operation, where the rules come from, and the full list of resources with write access. Use it before telling the user something is not possible.

Search or page any Manager collection, report feed or list (customers, sales_invoices, payments, tax_codes, general ledger feeds, …). 'term' searches, 'sort_by' takes a column name, and date feeds accept from_date / to_date (YYYY-MM-DD). Unsupported parameters are reported back rather than silently dropped.

Fetch one record by its Key (GUID) in the exact shape Manager stores it. Always do this before an update, and use an existing record as the template for a create — Manager's field names are not guessable.

Create a record (invoice, payment, customer, journal entry, tax code, …). 'fields' is Manager-native JSON: copy the shape from manager_get on an existing record of the same resource. Returns the new Key. For resources the catalog marks risk='high', get an explicit yes from the user first.

Update a record. For resources the catalog marks risk='high' (accounts, tax codes, rates, opening balances, settings) confirm with the user first — those changes restate existing books. Default mode 'merge' reads the live document first and changes only the fields you pass, which is what you normally want because Manager's PUT replaces the whole document. Use mode='replace' to send the body verbatim.

Delete a record permanently. Manager has no undo, so confirm with the user first; the deleted document is returned in the response so it can be re-created if needed.

Escape hatch: GET any Manager API path directly (e.g. '/customers' or '/sales-invoice-form/{key}'). Only for paths the catalog does not model. Requires 'Raw read' in the control panel.

Escape hatch: send any method (POST/PUT/DELETE) to any Manager API path. Bypasses per-resource tick boxes, so it requires the separate 'Raw write' box in the control panel. Prefer manager_create / manager_update.

Turn a file into something Manager will accept as evidence. Manager's Image field silently rejects PDFs, so ALWAYS run this on any PDF before attaching it: it rasterises every page and returns the image paths. Images pass through untouched. combine='vertical' (or 'horizontal') joins the pages of ONE document — a statement, a contract — into a single image, which is the right shape when the pages are one document. Leave combine='none' when the PDF holds several different documents, and never merge two different proofs into one image: each proof is its own attachment.

Re-read the Manager instance's own API description and rebuild the resource catalog. Run this after upgrading Manager or when a resource seems missing.