Busy Accounting · Busy API
Busy Accounting API: Data Contracts and Outputs
For developers connecting Busy data to a CRM, dashboard or ordering application, start with the data contract: which company and period, which fields, which response format and which errors the receiving application must handle.
The architecture below is a scoping example. Obtain the current endpoint documentation and confirm enabled reports, credentials, filters, limits and deployment prerequisites for your account. No endpoint or sandbox access is granted by this page.
Illustrative workflow
Application requests data
Pass only the company, party and date filters authorized by the agreed contract.
Connector obtains records
Use the configured Busy source or synchronized snapshot; establish its freshness.
Map and format
Apply the selected report mapping or reviewed custom query and output format.
Application handles response
Validate fields and handle empty, stale, denied or failed results before displaying or acting.
Standard mapping or a custom query?
Compare the implementation work for your data requirement. Neither option implies unrestricted database access or a guaranteed setup date.
On a narrow screen, scroll the table horizontally to read every column.
| Decision | Standard mapping | Custom query |
|---|---|---|
| Data shape | Use a confirmed report schema | Agree fields, joins and calculations |
| Filters | Confirm supported company/party/date filters | Review additional voucher or branch rules |
| Maintenance | Check schema/version compatibility | Retest business logic when the source changes |
| Fit | A receiving app can use the mapped report | The required report differs from the available mapping |
Choose the ledger output for the receiving app
Confirm which formats your endpoint supports. A PDF is a document; JSON still needs application logic; HTML still needs safe rendering and styling review.
JSON
Structured rows for a custom interface or downstream calculation: bill reference, date, debit/credit and balances as defined by the schema.
HTML
A display-oriented ledger if available. Review escaping, accessibility and layout before embedding it in a portal.
A printable statement if configured. Check the selected party, period and document fields before sharing.
Report contracts to request
Ask for the current routes, HTTP methods, authentication, schemas and error responses for ledger, outstanding, sales, inventory and any HTML/PDF ledger variant. Paths shown in earlier illustrations were examples; they are not executable endpoints on this marketing website.
Developer documentation: confirm the current Busy-specific contract with the integration owner before using any endpoint.
Confirm access and operating limits
Review authentication, company boundaries, approved query scope, network restrictions, logging and retention with the integration owner. Obtain actual rate limits, timeouts and availability terms. Token access alone is not a guarantee of isolation or uptime.
Route the output to the right reader
A CRM may need party balances; a BI dashboard may need sales rows; an ordering portal may need stock and prices. Each target needs its own mapping and error handling. The API is the retrieval layer; WhatsApp automation, report viewing and Sheet refresh are separate consumers.
What a technical scope should contain
Provide your Busy version, company selection, sample schema with private values removed, expected volume and receiving application. Agree authentication, permissions, freshness, pagination if needed, error/retry behavior and a permitted test environment. Confirm the production release and support terms separately.
Questions about Busy API
Must the Busy computer stay online?
It depends on the connector and deployment. A cloud snapshot can serve only the data already synchronized; new local changes need an available source connection. Agree freshness and outage behavior before relying on it.
Can a custom query access any Busy data?
Do not assume that. Confirm the supported schema, licensed features, permission scope and reviewed query with the owner. Company, financial-year, branch and voucher filters depend on the actual contract.
Are API calls unlimited?
No unlimited-call promise is made here. Obtain the account's limits, expected volume, timeout and retry policy in writing. Design for throttling and failed requests.
Which formats and endpoints are available?
The planning choices are JSON data, display-oriented HTML and printable PDF ledgers. Obtain current endpoint documentation to confirm which report and format combinations are enabled; the website does not execute them.
Choose the next workflow
Review privacy terms and the Legal Center. Confirm support and availability in your signed service agreement.
Discuss your Busy API setup
An enquiry does not book an appointment or activate a product. Availability, setup, support and commercial terms need separate confirmation; binding commitments require a signed agreement.
Send an enquiry