A common question from growing businesses is whether SQL Account can be connected to their other software instead of someone re-typing data between systems. It can. SQL Account provides a RESTful API that lets an external system create, read, update and delete records in SQL Account programmatically — so a confirmed order in your web store can become a Sales Invoice automatically, and your stock and customer lists stay in sync. Below is a plain-English overview of what it does and what's involved, and we're happy to guide the setup for you.
What the SQL Account API can connect
The API works with the core business records you already use in SQL Account. These are the main objects it exposes:
| Business object | What you can do with it |
|---|---|
| Sales Invoice | Turn confirmed orders from an external system into SQL Account sales invoices. |
| Purchase Invoice | Bring supplier bills from procurement systems into your purchases. |
| Stock Item | Read and update stock item data for catalogues, portals and dashboards. |
| Stock Transfer / Received | Move and receive stock across locations from external workflows. |
| Maintain Customer | Keep customer records aligned with your CRM, portal or sales tools. |
| Customer Payment | Post received customer payments from external payment or finance flows. |
| GL Payment Voucher / Journal Entry | Create finance-side postings from approved external processes. |
| Sales Order → Sales Invoice | Convert orders through to invoices as part of an automated flow. |
Output is available as JSON for data exchange, and PDF for document retrieval.
Common ways businesses use it
- E-commerce orders → Sales InvoiceSend confirmed Shopee, Lazada, TikTok or web-store orders straight into SQL Account as invoices, cutting manual entry for sales and finance.
- Supplier bills → Purchase InvoiceConnect procurement or supplier systems so bills flow into your accounting instead of being keyed in twice.
- CRM ↔ customer recordsKeep customer details in your CRM or portal aligned with SQL Account's Maintain Customer.
- Stock sync to external toolsFeed Stock Item data to warehouse tools, customer portals and operational dashboards.
- Finance postings from workflowsGenerate Journal Entries, Customer Payments and GL Payment Vouchers from approved external workflows.
How the integration works
- Request API credentials. An access key and secret key are issued for your specific SQL Account database through the onboarding process (we recommend a dedicated API user).
- Test with Postman. Use the ready-made Postman collection to confirm request signing, required fields and how each module behaves before you write any code.
- Send & retrieve JSON. Create, update, delete and read records using structured JSON payloads and the documented field rules; PDF document retrieval is supported too.
- Move into live integration. The same hosted API approach is used for demo and production, so you switch environments by swapping credentials, not rebuilding.
What you'll need
- SQL Account version 5.2025.1038.875 or above.
- Firebird database 3.0.9 or above recommended.
- Windows 11 (64-bit) recommended for the SQL Account / integration machine.
- Stable internet through a proper router or office network — not a mobile hotspot — so the environment can reach the API endpoint reliably.
- Some programming capability for request signing, field mapping and error handling — it's built for developers, integration partners or middleware, not browser-only use.
Security
The API is built for server-side integrations that need authenticated access to SQL Accounting data without exposing credentials in a browser. Requests use AWS SigV4 authentication over an HTTPS endpoint, and the access key and secret key are issued for your specific database — so it suits controlled back-end, middleware and automation services rather than client-side apps.
How we help you set it up
As an authorised Klang Valley SQL dealer, we make the starting line easier: we help you get on a supported SQL Account version, create a dedicated API user, generate and safely hand over your access and secret keys, and confirm your environment can reach the API reliably. From there we guide your developer or integration partner through the first working requests — or scope the whole integration with you if you'd rather not build it in-house. If you run SQL X-Store or sell across marketplaces, we can advise whether the API or an existing module is the better fit.
Official SQL API documentation
When your developer is ready to build, these are the official SQL references for the deep technical detail — setup flow, full endpoint docs, and the Postman collection:
Frequently asked questions
Does SQL Account have an API?
Yes. SQL Account provides a RESTful API (REST API 2.0) that lets external systems create, read, update and delete records such as sales invoices, stock items, customers and payments programmatically.
What can I integrate with the SQL Account API?
Common integrations include e-commerce orders into Sales Invoices, supplier bills into Purchase Invoices, CRM-to-customer syncing, stock data feeds, and finance postings like journals and customer payments.
How is the SQL Account API secured?
Requests use AWS SigV4 based authentication over HTTPS, with an access key and secret key issued for your database. It's designed for server-side use, so credentials aren't exposed in browser clients.
Do I need a developer to use it?
Yes. The API is built for technical teams, in-house developers or implementation partners. If you don't have a developer, we can help scope the integration and guide the setup.
Which version of SQL Account do I need?
SQL Account version 5.2025.1038.875 or above, with Firebird 3.0.9 or above recommended. We can check and update your version as part of setup.
Can DLS Technology set up the API integration for us?
We help you generate credentials, configure the environment, and get your first requests working — then guide your developer or integration partner through connecting it to your systems. Book a free consult and we'll scope it with you.