Security
Secure accounting API access without opening inbound ports
AcctBridge uses an outbound tunnel model so accounting machines do not need inbound firewall rules, static IPs, or public database exposure.
SQL Accounting and AutoCount API gateway
AcctBridge connectslocal accounting softwareto your software API.
Add a secure REST API to your SQL Accounting or AutoCount installation — no VPN, no static IP, no inbound firewall changes required.
api.acctbridge.combrand routed
# SQL Accounting connector
GET /v1/sqlacc/customer-invoice
Authorization: Bearer lb_live_...
# AutoCount connector
GET /v1/autocount/debtors
Authorization: Bearer lb_live_...
200 OK
{
"connection": "company-sqlacc",
"brand": "sql_accounting",
"data": [
{ "doc_no": "INV-00142", "status": "outstanding" }
]
}Why AcctBridge
Four problems every accounting API project runs into.
Building a custom on-premise connector is rarely worth it — weeks of engineering time upfront, then permanent maintenance. AcctBridge handles the access layer so your team doesn't rebuild it for every project.
01
Accounting software has no REST API out of the box
AcctBridge answer
AcctBridge installs a brand-specific local connector that exposes documented REST endpoints for SQL Accounting and AutoCount — COM BizObjects for SQL Accounting, SQL Server access for AutoCount.
02
Company networks block inbound connections
AcctBridge answer
The connector uses outbound HTTPS only. No port forwarding, no static IP, no firewall rule changes needed on the accounting machine's network.
03
Every project rebuilds the same access layer
AcctBridge answer
One portal, one installer, one setup flow. The same pattern — create connection, install connector, verify, call API — repeats for the next branch, company, or accounting instance.
04
Who sees your financial data when it passes through a cloud gateway?
AcctBridge answer
AcctBridge never stores accounting payloads. Invoices, payments, and customer records are proxied in real time — directly from your connector to the requesting app. We retain only operational signals: timestamps, status codes, and latency. Nothing financial.
Implementation path
One consistent integration. Brand-specific endpoints.
Three steps: create an account, install the connector, call the API. SQL Accounting and AutoCount each have their own API prefix, while onboarding, auth, tunnel provisioning, and monitoring stay consistent.
01
Create an account and download the installer
Sign up, select your accounting brand (SQL Accounting or AutoCount), and download the connector package from the portal.
02
Install on the Windows accounting machine
Run the installer on the machine where the accounting software runs. It sets up the local agent and outbound tunnel with guided defaults.
03
Call the API and verify the connection
Use the portal connection check to confirm the connector is live, then call the brand-specific API endpoint with your API key.
🌏
SQL Accounting and AutoCount across SEA
Built around accounting software used across Southeast Asia, with Malaysia-first operations and PDPA-aware data minimisation.
📦
Self-install in minutes
Download the Windows connector from the portal, run it on the accounting machine, and verify readiness with built-in diagnostics — minimal IT coordination for most sites.
📡
Live tunnel and connector status
The portal shows real-time tunnel connectivity, connector health, and latency for each accounting connection — so you always know if the link is alive.
🔬
API test probe built in
Fire live API calls from the portal before writing integration code. See the response body, status, and latency without setting up Postman.
Start free, then scale by accounting instance.
Start with 30 days of free access. Paid plans show clear pricing before signup or checkout.
Free
US$0
30-day trial
Test one accounting workflow before paid access.
- One trial accounting instance
- Portal access
- SQL Accounting or AutoCount API evaluation
- Installer and tunnel setup for testing
- API key setup for trial validation
- Email support
Launch
US$49
per month
For the first managed accounting instance.
First paid month includes 1 extra month of access.
- One managed accounting instance
- Full portal access
- AcctBridge gateway API for SQL Accounting or AutoCount
- Generated installer, tunnel, and API key
- Portal connection checks and install diagnostics
- Email support
★ Most Popular
Scale
US$199
per month
Billed monthly for multiple accounting instances.
First paid month includes 1 extra month of access.
- Includes Launch benefits
- Up to 5 managed accounting instances
- Multi-branch or multi-company setup support
- Usage, uptime, and connection visibility
- Higher technical support coverage
- Faster support response for rollouts
Custom
Written quote
Custom pricing is quoted before rollout.
For more than 5 instances, branches, companies, or partner needs.
- Custom accounting instance count above Scale
- Custom workflow or integration planning
- Commercial or partnership discussion
- Commercial terms by agreement
- Dedicated setup coordination
- Support coverage agreed in writing
Public signup starts the first accounting connection for the selected brand. Launch and Scale subscriptions are purchased in the portal through Creem. New paid Launch and Scale customers receive one extra month of access after payment confirmation; the extra access is applied manually and does not change the recurring subscription price. Prices are shown excluding tax; any applicable tax is added at checkout. Prices for all plans, including custom, may change for future purchases and at renewal with prior notice; custom setups are opened with support assistance.
Partner program
Partner with AcctBridge.
We work with SQL Accounting and AutoCount implementers, ISVs, local IT consultants, and reseller partners who serve Malaysia and Southeast Asia SMEs.
Approved partners can refer qualified customers or support multi-company rollouts. Referral and revenue-share terms are agreed in writing before any commercial work begins.
Referral partners
Introduce qualified SQL Accounting or AutoCount integration opportunities from customers who already need a reliable API gateway.
Implementation partners
Support rollout planning, agent installation, first workflow validation, and handover for accounting installations.
Reseller partners
Coordinate multi-company or multi-branch rollouts with agreed support ownership, commercial terms, and written reseller coverage.
Public partner copy does not create commission, reseller, or revenue-share rights. Commercial terms vary by role, rollout volume, payment method, refund exposure, and support ownership, and must be confirmed in a written agreement.
From the blog
Implementation notes on setup, security, and data flow.
Use case
Write POS and ecommerce records into SQL Accounting or AutoCount
Use AcctBridge as the API layer for POS, Shopify middleware, ecommerce, OMS, or custom apps that need to write supported accounting records into SQL Accounting or AutoCount.
Security
A zero-persistence API gateway for accounting payloads
AcctBridge proxies supported SQL Accounting and AutoCount requests in real time and avoids storing customer financial payloads in the hosted control plane.
Frequently asked questions.
Integration inquiry
Tell us about your integration.
Share your accounting system, company or team context, and the first workflow you need to connect.
Technical support
For installer, tunnel, connection check, or API connection issues, email support@acctbridge.com. We use portal status and diagnostics to help review the next step quickly.
Consulting and custom needs
For workflow mapping, rollout questions, or custom integration planning, email hello@acctbridge.com or use this form. We will reply with scope questions and next steps.
Partnership discussions
For reseller, integrator, referral, or multi-company partnership discussions, contact hello@acctbridge.com. Partner and revenue-share terms must be agreed in writing before commercial work begins.
Start with the connector your accounting system uses.
Create an account, install the matching local agent, and make the first brand-specific API call from your own app.
Account access uses email verification and connector packages generated from your portal.