Human reference

AutoCount Cloud API Documentation

Use this API to let software, OpenClaw, or AI tools read and operate AutoCount Accounting 2.2 through the local Windows connector. The public cloud API receives requests, then relays them to the customer's connector by outbound polling.

1. Sign Up

Create a customer account, get a tenant API key, and download the connector setup package.

GET /signup

2. Local Connector

Download Installer, install the Windows connector on the licensed AutoCount machine, import the cloud config, and add one or more account books.

GET /downloads/AutoCountConnectorSetup.exe

3. API Calls

Send commands to the cloud API with the tenant key. The connector executes them locally and returns the result.

POST /v1/commands

Customer Portal Endpoints

Endpoint	Purpose
`GET /login`	Customer login page.
`GET /portal`	Dashboard with subscription, connector ID, account books, installer, and config download.
`GET /app/state`	Authenticated JSON state for the customer dashboard.
`GET /app/connector-config.json`	Authenticated connector config JSON for one-click import.

Tenant API

External apps call these with Authorization: Bearer <tenantApiKey>. Always send a unique commandId for idempotency and audit.

Endpoint	Purpose
`POST /v1/commands`	Queue a read or write command for a connector and account book.
`GET /v1/commands/:id`	Check command status and read the final result.

{
  "commandId": "invoice-count-20260612-001",
  "connectorId": "customer-connector-id",
  "companyId": "macsofttest",
  "type": "sales.invoice.count",
  "payload": {}
}

Connector API

The local connector uses these cloud endpoints with its connector key. Customers do not call these directly.

Endpoint	Purpose
`GET /connectors/:id/commands/next`	Connector polls for the next command.
`POST /connectors/:id/commands/:commandId/result`	Connector posts command result or error.
`POST /connectors/:id/companies`	Connector reports configured account books.
`POST /connectors/:id/heartbeat`	Connector reports service health.

Important Safety Rules

Read access should be the default for trials.
Write access should require subscription plan, explicit account book permission, command idempotency, and audit logs.
AutoCount credentials stay encrypted on the customer's Windows machine.
No inbound firewall or router opening is required because the connector calls out to the cloud.