Connect. Automate. Scale
SQL Accounting REST API Integration Service
Automate data exchange, reduce manual rekeying, and speed up integration projects with Postman resources, documented payloads, and starter examples for common development stacks.
Everything You Need to Integrate Faster
From secure authentication to ready examples and supported workflows, everything is in place to help your team connect and launch faster.
❮
AWS SIGV4 AUTHENTICATION
Secure system-to-system requests
POSTMAN COLLECTION
Test faster with ready requests
JSON AND PDF WORKFLOWS
Support data exchange and document retrieval
PROGRAMMING LANGUAGES
Starter examples in popular languages
DOCUMENTED OBJECTS
Work with invoices, stock, payments, and more
❯
SUPPORTED WORKFLOWS
Work with GST and SST enabled SQL accounting workflows
Connect sales, purchase stock, customer, payment, journal, and transfer workflows
Create, edit, delete, and retrieve business records
Support live and batch data updates
What You Can Work With
Explore the business objects and output formats available in the current API documentation.
Business Objects
Stock Transfer
Maintain Customer
Stock Received
Agent
Stock Item
Journal Entry
Sales Invoice
GL Payment Voucher
Purchase Invoice
Customer Payment
Sales Order to Sales Invoice
Available Output Formats
How It Works
Start in a controlled test environment, validate your payloads, then move into production onboarding with the same integration approach
❮
Request API
Credentials
Access key and secret key are issued through the onboarding process for controlled API usage.
Test Endpoints with Postman
Use the provided collection to confirm request signing, required fields, and module behavior.
Send and Retrieve JSON Records
Create, update, delete, and retrieve data using structured payloads and documented field rules.
Move Into Live Integration
Use the same hosted API approach for demo and production onboarding, guided by provider-issued credentials.
❯
How to Start
Use the resource set to move from first request to production planning with less guesswork.
01
Step 1
Download Postman
Collection
Import requests quickly and validate authentication, headers, and endpoint behavior
Step 2
02
Setup and
Configuration
Follow the SQL Account API setup flow for provider-issued credentials and configuration
03
Step 3
View Sample Payloads
Review minimum-field JSON examples before mapping fields from your external system.
Step 4
04
Browse Code
Examples
Start from language-specific examples for common implementation stacks.
05
Step 5
Review Field Details
Use field references to plan mapping, validation, and required data handling.
Step 6
06
Read Integration FAQ
Check common request patterns, limits, and JSON structure guidance
07
Step 7
Discuss Your
Integration
Speak with the SQL team when you are ready to confirm fit, onboarding, and next steps.
Build in the language your team uses
Explore ready-to-use guides for the languages and platforms your team already work with
PHP
C#
GAS
Node.js
Python
$ch = curl_init(); curl_setopt($ch, CURLOPT_URL, "http://localhost:8080/api/Customer"); curl_setopt($ch, CURLOPT_HTTPHEADER, ["Authorization: Bearer YOUR_TOKEN"]); $result = curl_exec($ch);
var client = new HttpClient(); client.DefaultRequestHeaders.Add( "Authorization", "Bearer YOUR_TOKEN"); var res = await client.GetAsync( "http://localhost:8080/api/Customer"); var body = await res.Content.ReadAsStringAsync();
function getCustomer() { var url = "http://localhost:8080/api/Customer"; var opts = { headers: { "Authorization": "Bearer YOUR_TOKEN" } }; var res = UrlFetchApp.fetch(url, opts); Logger.log(res.getContentText()); }
const axios = require('axios'); const res = await axios.get( 'http://localhost:8080/api/Customer', { headers: { 'Authorization': 'Bearer YOUR_TOKEN' } }); console.log(res.data);
import requests headers = {"Authorization": "Bearer YOUR_TOKEN"} res = requests.get( "http://localhost:8080/api/Customer", headers=headers) print(res.json())
A solid choice for web service and event-driven application.
- Suitable for web-based integrations projects
- Invoice & document workflow examples
A solid choice for web service and event-driven application.
- Good fit for internal tools and back-end systems
- Downloadable GET & POST examples
A solid choice for web service and event-driven application.
- Helpful for Google Workspace-based processes
- Suitable for simple sales and finance automation flows
A solid choice for web service and event-driven application.
- Well suited for API gateways and automation services
- JSON workflow & PDF retrieval examples
A solid choice for web service and event-driven application.
- Strong fit for middleware and server-side jobs
- Includes reusable examples for signed API requests
$ch = curl_init(); curl_setopt($ch, CURLOPT_URL, "http://localhost:8080/api/Customer"); curl_setopt($ch, CURLOPT_HTTPHEADER, ["Authorization: Bearer YOUR_TOKEN"]); $result = curl_exec($ch);
using var client = new HttpClient(); client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", token); var res = await client.GetAsync( "http://localhost:8080/api/Customer");
function getCustomers() { const res = UrlFetchApp.fetch( "http://your-server/api/Customer", { headers: { Authorization: "Bearer TOKEN" } }); Logger.log(res.getContentText()); }
const axios = require('axios'); axios.get('http://localhost:8080/api/Customer', { headers: { Authorization: 'Bearer YOUR_TOKEN' } }) .then(res => console.log(res.data))
import requests headers = {"Authorization": "Bearer YOUR_TOKEN"} res = requests.get( "http://localhost:8080/api/Customer", headers=headers ) print(res.json())
Security
The API is designed for server-side integrations that need authenticated access to SQL Accounting data without exposing credentials in browser-based clients.
Requests use AWS SigV4 based authentication
HTTPS endpoint for encrypted transport
Access key and secret key are issued by the provider
Suitable for controlled back-end, middle-ware, and automation services
Requirements
Prepare the right software version, network setup, and technical resources before starting an API integration project.
SQL Accounting and
Environment Requirements
SQL Accounting Version 5.2025.1038.875 or above.
Firebird Version 3.0.9 or above is recommended.
Microsoft Windows 11 and above is recommended, preferably 64-bit.
Internet access is required for the machine, server, or hosted environment where SQL Accounting and the integration process are running.
The connection should come from an ISP (Internet Service Provider) with proper router or office network access so that environment can reach the API endpoint reliably.
Mobile phone data, personal hotspots, or ad-hoc mobile connections are not recommended as the main integration connection.
Credentials and
Setup Process
Access Key and Secret Key are issued by the provider for the target database.
The same API endpoint domain is used for demo and production/live onboarding, so credential management should clearly separate environments.
Router, firewall, and outbound network access should allow the SQL Accounting environment to reach the API end point consistently.
Implementation
Capability Required
Programming knowledge is required for request signing, payload mapping, and error handling.
The API is intended for technical teams, implementation partners, or back-end/middle-ware workflows.
Standalone environments and browser-only client-side usage are not the intended setup.
For best stability, the integration should run from a proper office, server, or hosted environment instead of depending on a mobile device connection.
Ways to Use The API
Use the API to connect daily business activity with accounting records and stock workflows.
Sync Only Orders Into Sales Invoice
Send confirmed e-commerce orders into SQL Accounting as Sales Invoices, reducing manual entry for sales and finance teams.
Push Supplier Bills Into Purchase Invoice
Connect procurement or supplier systems to Purchase Invoice workflows so supplier bills can move into accounting more smoothly.
Generate Finance-Side Posting from External Workflows
Create finance-side records such as Journal Entry, Customer Payment, and GL Payment Voucher from approved external workflows.
Create and Update Customer Records from CRM
Keep customer details from CRM, portals, or sales tools aligned with Maintain Customer records in SQL Accounting
Pull Stock Item Data for External Catalogue Sync
Use Stock Item data to support catalogue updates, customer portals, warehouse tools, and operational dashboards.
❮
Sync Only Orders Into Sales Invoice
Send confirmed e-commerce orders into SQL Accounting as Sales Invoices, reducing manual entry for sales and finance teams.
Push Supplier Bills Into Purchase Invoice
Connect procurement or supplier systems to Purchase Invoice workflows so supplier bills can move into accounting more smoothly.
Generate Finance-Side Posting from External Workflows
Create finance-side records such as Journal Entry, Customer Payment, and GL Payment Voucher from approved external workflows.
Create and Update Customer Records from CRM
Keep customer details from CRM, portals, or sales tools aligned with Maintain Customer records in SQL Accounting
Pull Stock Item Data for External Catalogue Sync
Use Stock Item data to support catalogue updates, customer portals, warehouse tools, and operational dashboards.
❯
Built for Faster Accounting Workflows
Move routine accounting data between systems with fewer delays, fewer hand-offs, and documented workflow example.
Eliminate
Duplicate Entry
Sync Sales Invoice, Maintain Customer, Stock Item, and accounting records directly from external systems.
Accelerate
Implementation
Start with Postman, minimum-field sample JSON, and language examples instead of building every request from scratch.
Support Real
Workflows
Handle create, update, delete, retrieval, PDF document retrieval, and document-driven processes.
Best for:
Implementation partners and ERP integrators
In-house developers and middle-ware teams
Portal builders and automation teams
01Onboarding FAQ
The environment is determined by the Access Key and Secret Key issued for the target database. The API host does not display a separate sandbox or production label, so each credential pair should be stored and named clearly in your integration configuration.
Most API endpoints use the same host and path structure for both sandbox and production. For example, Sales Invoice uses https://api.sql.my/salesinvoice and Stock Item uses https://api.sql.my/stockitem. These URLs are API endpoints only, so not show a webpage when opened directly in a browser.
Both are able to be get by following the steps given inside this guide https://docs.sql.com.my/sqlacc/integration/sql-account-api/setup-configuration. Recommended clients to create a brand new user inside maintain user just for API Service (E.G. APIUSER). After saving new created user, press more... | Generate Secret Key, and click yes, both key will appeared. Make sure user have copied both Access key and Secret Key below closing the Window as the Secret Key only can be copy when first time open.
Client can email to support@sql.com.my to request for demo public account or sandbox credentials, same if they want to request meeting with us.
02Implementation FAQ
