Skip to content

Custom web apps and APIs

Give your own apps the BUSY data they need

Your website, dealer portal or mobile app calls the AI Zeny API for prices, stock, ledgers or invoices, and receives one predictable JSON envelope. Orders it collects can become BUSY vouchers once you authorize them.

Configurable JavaScript pattern — built with your own scripts and your own provider account; not a native connector

Start Free Trial

Free trial · no card or payment details · Pro-level features, without the AI Agent

The problem it solves

  • An app shows prices or stock that are days out of date because they were uploaded by hand.
  • Dealers or customers phone in to ask for a ledger or an invoice copy.
  • Orders taken in an app are re-typed into BUSY.

How it fits together

  1. Step 1: Your app calls the API

    With a token limited to the companies it needs.
  2. Step 2: It shows or uses the answer

    Prices, stock, a ledger or an invoice from BUSY.
  3. Step 3: Orders come back with approval

    Orders from the app can be prepared as vouchers and posted after you authorize them.

BUSY data it reads

Products, one page · Latest date-wise prices · Customer ledger (one or more years) · Sale invoices · Product lines of one sale invoice

What you need to set up

  • A developer who can call an HTTPS API with a bearer token.
  • An API token for the app, created in the portal.
  • Optionally, a script on your PC that sends BUSY data to your app’s own API, using the access your app gives it.

Plus reads your BUSY data, with scripting and Google Sheets; Pro adds accounting writes; Max adds the AI Agent, which is not available yet. Go, below Plus, includes none of these. Every plan, the free trial included, has the end-to-end encrypted BUSY backup. Local mode and Cloud mode are not tied to a plan. The free trial gives Pro-level features, without the AI Agent.

What you control

  • Each app gets its own token, limited to selected companies, optionally expiring.
  • Rotate or revoke a token without touching other integrations.

Scripts

Scripts are stored and run in the AI Zeny Windows app on your PC — also when you use Cloud mode — whether you write them yourself or the AI agent drafts them. Inactive scripts can run for previews and tests, and those runs have real effects; API use requires you to activate the script.

Voucher posting

A voucher is previewed and validated, and posted only after you authorize it; the AI agent never posts one by itself. If a posting fails or its result is unclear, check in BUSY whether it was posted before you try again.

Where the data goes

  • Your app receives BUSY data through the API; what it shows to its users is up to your app.

Local mode: Requests are answered by the AI Zeny Windows app on your PC. In ordinary operation AI Zeny does not persistently store the accounting data in those answers.

Cloud mode: encrypted snapshots synchronized approximately every 10–15 minutes, readable around the clock. Cloud-mode answers reflect the last completed synchronization, not live data.

Exception, in either mode: with your explicit consent, a small sample can be sent to OpenAI to correct a wrong AI-built query. AI Zeny deletes its own temporary copy after the correction; what OpenAI keeps is governed by OpenAI’s terms.

Limits

  • Standard read answers up to 2 MiB; larger answers are refused, never cut short.
  • A standard read request waits up to 140 seconds. Write and streaming operations have their own limits in the operation reference.

These are technical limits of each request and apply the same way on every plan and during the free trial. The free trial also has its own length and company, financial-year and device limits, shown on the free-trial page and when you register.

Start Free Trial

Free trial · no card or payment details · Pro-level features, without the AI Agent