SQL Accounting and AutoCount API gateway

AcctBridge connectslocal accounting softwareto your software API.

Give each SQL Accounting or AutoCount installation a secure REST API through a local installer, outbound tunnel, tenant portal, and brand-specific endpoints.

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
{
  "tenant": "client-42",
  "brand": "sql_accounting",
  "data": [
    { "doc_no": "INV-00142", "status": "outstanding" }
  ]
}

Integrator pain

Turn client-site setup into a repeatable rollout process.

AcctBridge packages the access layer so each project can start from a working tenant with installer, tunnel, auth, API keys, and connector monitoring already aligned.

Local API

Every client starts with local access work

You still need an agent beside the accounting software, local credentials, service recovery, and a reachable HTTPS path.

Network

Outbound access keeps client sites simpler

The local connector uses outbound HTTPS, which keeps setup practical for client environments with limited firewall and router administration.

Brand logic

Purpose-built connectors for each accounting system

AcctBridge packages the right local connector for SQL Accounting or AutoCount, then exposes documented REST endpoints your software can call consistently.

Delivery

Repeatable rollout keeps projects moving

A templated setup path lets your team focus project time on workflow logic instead of rebuilding the access layer for each client.

What AcctBridge adds

Pain-free installation

Setup designed for non-specialists

The installer handles the agent and tunnel setup. Most teams can install and run the portal connection check without bringing in specialist network support.

Observability

Always know the connection status

The tenant portal shows tunnel status, connector health, install diagnostics, and connection checks so support starts from evidence.

Fast rollout

Standardised process scales without extra headcount

Register, install, verify, then repeat for each client. The same operating steps reduce support effort as customer count grows.

Implementation path

One consistent integration. Brand-specific endpoints.

Three steps: create a tenant, 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 a tenant 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 client Windows 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 tenant key.

API coverage

Clear REST APIs for each accounting platform.

Your integration calls documented SQL Accounting or AutoCount endpoints while AcctBridge handles tenant routing, secure access, and connector operations.

SQL Accounting

.NET local agent with COM BizObjects

/v1/sqlacc
Customer invoice
Customer payment
Credit note knock-off
Stock item
Supplier
View SQL Accounting details

AutoCount

Go local agent with SQL Server access

/v1/autocount
Debtor
Invoice
Payment
Credit note knock-off
Delivery order
View AutoCount details

Start free, then scale by accounting instance.

Start with 30 days of free access. Launch terms are available for early rollout teams and are confirmed before paid use begins.

Launch

Launch offer available. Terms are confirmed before paid use begins.

  • One managed accounting instance
  • Full tenant portal access
  • SQL Accounting or AutoCount native API
  • Generated installer, tunnel, and API key
  • Portal connection checks and install diagnostics
  • Email support
Start free
★ Most Popular

Scale

Priced by managed accounting instance count and support needs.

  • Includes Launch benefits
  • Multiple managed accounting instances
  • Per-instance commercial terms
  • Usage, uptime, and connection visibility
  • Higher technical support coverage
  • Faster support response for rollouts
Talk about rollout

Custom

Commercial terms are agreed around scope and partnership needs.

  • Custom accounting instance count
  • Custom workflow or integration planning
  • Commercial partnership discussion
  • Commercial terms by agreement
  • Dedicated rollout coordination
  • Support coverage agreed in writing
Talk to us

Public signup starts the first tenant for the selected accounting brand. Multi-client and custom rollouts are opened with support assistance.

🌏

SQL Accounting and AutoCount across SEA

Built around accounting software used across Southeast Asia, with a Malaysia-first rollout and PDPA-aware data minimisation.

☁️

Cloudflare Tunnel

Client sites use outbound tunnels, so integrations do not require inbound firewall changes or static IP setup.

📈

Operational visibility

Tunnel status, connection checks, install diagnostics, and usage metadata are visible for support.

🔑

Tenant boundary

Each accounting instance has its own tenant, API key boundary, selected brand, and local agent package.

Frequently asked questions.

Integration inquiry

Tell us about your integration.

Share the accounting system, company, studio, or client 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, or multi-client partnership discussions, contact hello@acctbridge.com. We can discuss instance volume, support coverage, and a first commercial structure.

0/2000

Start with the connector your client actually 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 installer packages generated from your tenant portal.