Blog
What an API means for a BUSY business, without the jargon
Your developer or software vendor says “we just need API access to BUSY”. Here is what that means in plain words, and which decisions stay with you.
Facts reviewed on
An API is a counter, not a door
Think of an API as a service counter in front of your BUSY data. Another program walks up, asks for one specific thing — “pending bills for this customer, this financial year” — and gets exactly that answer back. It never walks around the counter into BUSY itself.
With AI Zeny, the counter is answered by the AI Zeny Windows app on your PC, or in Cloud mode from a synchronized snapshot. Reading never changes your books.
Three words you will hear
- Request: one question in a fixed format, naming the BUSY company code and the financial year.
- Token: the key a program shows at the counter. You create one per program in the AI Zeny portal, limit it to the companies it needs, and can revoke it.
- Answer: always the same shape, so the program knows where to find the data and whether something went wrong.
The decisions that stay with you
- Which programs get a token, and for which companies.
- Whether requests go to your PC (Local mode) or to synchronized snapshots (Cloud mode).
- Whether anything is ever written back: vouchers are posted only after you authorize them.
Illustrative example — not a customer case
A wholesaler’s ordering app needs current prices. The owner creates one token for that app, limited to the company that holds the price lists. The app can read that company’s prices but not another company’s data, and nothing is posted into BUSY without the owner’s authorization.
For the details your developer needs, send them to the developer documentation.