The complete AutoCount Web API: every entity, every document, one REST surface.
A REST gateway over your AutoCount company books. Read and write master data and full documents - quotations, sales orders, delivery orders, invoices, receipts, purchase documents, journals - with the same numbering, defaults and transfer behaviour as the AutoCount desktop forms.
What it does
DAXONET AC Gateway puts a documented REST API in front of AutoCount Accounting. Every route is scoped to one account book, so a connection to your books is explicit: /v1/{accountBookId}/data/{entity} for data and /v1/{accountBookId}/services/{ServiceName} for operations that return a report.
It is not a read-only extract. Master data and documents are created, updated and deleted through the same AutoCount engine that the desktop application uses, so document numbering, debtor-derived defaults, item pricing, tax codes and approval states behave exactly as they do in AutoCount - including the document transfer chain, which can be performed in a single call.
Reporting is part of the API: the gateway lists the printout templates available in the account book, the AutoCount edition and the signed-in user's rights, then renders the document as a PDF on demand. Integrations are expected to discover templates rather than hard-code them.
Because it runs where AutoCount runs, your accounting data never leaves your network. The licence covers the gateway itself; the metered tiers below define how much daily traffic the licence allows.
Capability groups
Read and write
List, page, fetch by key, create, update and delete on masters and documents, plus $columns schema discovery for every entity.
Document workflow
Approve, void (alias cancel) and reject actions on documents, and the transfer chain from quotation through to invoice or receipt.
Master data
Debtors and creditors with all their tabs, stock items with prices and UOM, tax codes, currencies, agents, areas, branches and document numbering series.
Services and reports
Company profile, system health and fiscal period services; template discovery and PDF rendering for every registered AutoCount printout.
Technical specification
| Base URL | /v1/{accountBookId}/data/{entity} |
|---|---|
| Services | POST /v1/{accountBookId}/services/{ServiceName} |
| Authentication | OAuth2 password grant: POST /oauth/token, then Authorization: Bearer on every request. Tokens are valid for 3600 seconds. |
| Scopes | Token scopes are enforced per client, including an allow-list of account books and dedicated scopes for services and report generation. |
| Rate limit | 120 requests per minute per client; exceeding it returns 429. |
| Paging | ?page=1&pageSize=20; responses carry count, page, pageSize and totalPages. |
| Schema discovery | GET /data/{entity}/$columns returns the field list so integrations do not hard-code columns. |
| Actions | POST /data/{entity}/{docKey}/{action} with approve, void (alias cancel) or reject. |
| Document updates | A document PATCH replaces the detail lines, matching how AutoCount re-applies lines when a document is edited. |
| Printouts | List available templates, then render the chosen one to PDF. Availability varies by account book, AutoCount edition and user rights. |
| Errors | JSON error envelopes with HTTP status: 400 validation, 401 token, 403 scope or account book not allowed, 404 not found, 429 rate limit, 500 internal. |
Module coverage
Endpoint list of the published API 1.1 collection: 400 operations across nine modules.
| Module | Ops |
|---|---|
| Stock
Items, item groups, types, brands, categories, classes, prices, UOM, stock movements, stock takes and adjustments |
123 |
| Sales
Quotations, sales orders, delivery orders, sales invoices, cash sales, credit notes, consignment notes |
64 |
| AR
Debtors and AR receipts, AR invoices, AR debit / credit notes, AR refunds and deposits |
54 |
| AP
Creditors and AP payments, AP invoices, AP debit / credit notes, AP refunds and deposits |
54 |
| Purchase
Purchase orders, goods received notes, purchase invoices and purchase returns |
42 |
| Look Up / Reference
Areas, branches, agents, currencies, terms of payment, document numbering series, company profile |
28 |
| GL
GL accounts, journals, bank and cash entries, posting account groups, account types |
28 |
| Tax
Tax codes and tax entities for SST / GST and e-Invoice configurations |
6 |
| Auth token
OAuth2 password-grant token issue and refresh |
1 |
| Total | 400 |
The document chain, in one call each
A document can be created from its predecessor without leaving the API: send the source document and the lines to carry forward, exactly like ticking source lines in the AutoCount Transfer From dialog. Line-level transferred and pending quantities are tracked by AutoCount.
Sales Quotation ──▶ Sales Order ──▶ Delivery Order ──▶ Sales Invoice
│
▼
AR Receipt
Purchase Purchase Order ──▶ Goods Received Note ──▶ Purchase Invoice
│
▼
AP Payment
Also supported: cash sales, sales / purchase credit and debit notes,
consignment notes, GL journals, bank and cash entries.
Deployment and prerequisites
| Runs on | The Windows machine that hosts AutoCount Accounting, inside your network. |
|---|---|
| AutoCount | AutoCount Accounting with the company books you want exposed; a dedicated integration user is recommended. |
| Network | HTTPS from your integration to the gateway. No inbound internet exposure of AutoCount is required. |
| Clients | OAuth clients are issued per integration, with a scope set and an account-book allow-list, so one partner cannot reach another book. |
| Licence | Annual subscription by daily transaction tier, plus a one-time installation fee. The licence is issued and check-in managed by the CITS licence service. |
Choose a tier
All tiers include the full API surface - the difference is the daily transaction volume the licence allows. Prices exclude SST (8%).
1,000 transactions / day
- 1,000 / day API transactions
- All 9 modules, all 400 operations
- OAuth clients with scopes and account-book allow-list
- Template discovery and PDF printouts
- Upgrades from the licence channel
2,000 transactions / day
- 2,000 / day API transactions
- All 9 modules, all 400 operations
- OAuth clients with scopes and account-book allow-list
- Template discovery and PDF printouts
- Upgrades from the licence channel
Unlimited transactions
Most headroom- Unlimited API transactions
- All 9 modules, all 400 operations
- OAuth clients with scopes and account-book allow-list
- Template discovery and PDF printouts
- Upgrades from the licence channel
First installation RM 1,000 + SST is a one-time charge covering gateway installation, account-book connection, the first OAuth client and go-live checks. A "transaction" is one API request that reads or writes data.
Questions we are asked
Does it write into AutoCount?
Yes, when the client is given write scope. Documents are created through AutoCount's own engine, so numbering, defaults, pricing and approval states match the desktop application, and your audit trail stays intact.
How is a transaction counted?
One API request that reads or writes data. Token requests and rate-limit rejections are not counted against the daily tier; the tier is there to keep traffic predictable and supportable.
Can one integration see all our companies?
Only if you allow it. Each OAuth client carries its own scope set and an account-book allow-list, so a partner integration can be confined to the books it needs.
Do we still need the CITS AutoCount Bridge?
They solve different jobs. The bridge is a local assistant-facing API in front of one company database with native printouts; the gateway is the broad integration surface across entities, documents and modules. Many customers run both.
How do we find the right fields?
Ask the entity for its schema with $columns. The published endpoint list and the API documentation describe every route, field and error an integration will meet.
What happens if we exceed the tier?
The gateway keeps serving; the tier is a commercial measure of volume, reviewed with you. Request-rate limits (120 per minute) are separate and are there to protect AutoCount.