Quick Start

First SQL Accounting API call
— in 5 minutes.

Use the SQL Accounting connector when your accounting environment runs SQL Accounting on a Windows machine with COM BizObjects access. The portal flow stays the same; the API path and local connector are brand-specific.

Before you begin

✓

AcctBridge account

Create an account or sign in to an existing portal account

✓

SQL Accounting instance connected

Installer package run on the accounting Windows machine, then verified from the portal

✓

API key generated

Dashboard → API Keys → Generate New Key

30 seconds

Get your API key

In your AcctBridge dashboard, go to API Keys and click Generate New Key. Your key looks like this:

lb_live_xxxxxxxxxxxxxxxxxxxx

⚠ Keys start with lb_live_. Keep it secret — it grants access to accounting data.

10 seconds

Verify your tunnel is online

In the dashboard, go to Instances. The instance status must show Connected before API calls will succeed.

Tunnel shows Offline? The accounting PC is not running or the local accounting agent service has stopped. Run the installer package from the portal as Administrator, then use Check connection to verify reachability.

Any language

Make your first call

Read a bounded SQL Accounting V2 customer page. In the sample, replace lb_live_YOUR_API_KEY with the key you generated in Step 1.

curl -X GET "https://api.acctbridge.com/v1/sqlacc/reference-data/customers?PAGE=1&PAGE_SIZE=1" \
  -H "Authorization: Bearer lb_live_YOUR_API_KEY"

200 OKResponse

{
  "items": [
    {
      "fields": {
        "CODE": "300-A001",
        "COMPANYNAME": "Sunrise Trading Sdn Bhd",
        "CURRENCYCODE": "MYR"
      }
    }
  ],
  "pageInfo": { "page": 1, "pageSize": 1, "hasNext": false }
}

That's it. The SQL Accounting V2 public surface is read-only; use the documented GET paths and bounded query parameters.

Selected SQL Accounting endpoints

All paths are prefixed with https://api.acctbridge.com. Authenticate with Authorization: Bearer <key>.

Reference data

GET	/v1/sqlacc/reference-data/customers?CODE={code}	Read one customer by exact code
GET	/v1/sqlacc/reference-data/customers?PAGE=1&PAGE_SIZE=50	Read a bounded customer page

Sales compliance

GET

/v1/sqlacc/sales/e-invoice-status?DOCDATE_FROM={date}&DOCDATE_TO={date}

Accounts receivable

GET	/v1/sqlacc/ar/invoices?PAGE=1&PAGE_SIZE=50	Read a bounded AR invoice page
GET	/v1/sqlacc/ar/invoices?DOCNO={docno}	Read one AR invoice with line fields
GET	/v1/sqlacc/ar/statement?CODE={code}&DATE_FROM={date}&DATE_TO={date}	Generate a customer statement

Common errors

Status	Code	Meaning	Fix
401Unauthorized	api_key_invalid	Key is wrong, expired, or deactivated	Regenerate in Dashboard → API Keys
503Service Unavailable	tunnel_offline	Accounting PC is offline or local agent is stopped	Run the portal installer, then check the agent connection
429Too Many Requests	rate_limited	Request rate is temporarily limited	Reduce bursts or polling frequency
502Bad Gateway	upstream_error	The local accounting agent returned an unexpected error	Check agent logs on the accounting machine
530Tunnel Unreachable	tunnel_unreachable	Cloudflare cannot reach the tunnel — connector is offline or tunnel has disconnected	Open the portal, check tunnel status, and restart the connector on the accounting machine

Quick start FAQ

Can I test SQL Accounting and AutoCount APIs from the same quick start?

Yes. The quick start shows both SQL Accounting and AutoCount first-call examples. Each accounting connection uses its own software selection, API prefix, local agent, tunnel, and API key.

What do I need before making the first API call?

Create or sign in to the portal, install the connector package on the accounting Windows machine, verify the tunnel is connected, and generate an API key.

Can I import the API docs into Postman?

Yes. Use the public Swagger docs for a clean OpenAPI import, or download connection-specific docs from the portal when you need the endpoint and API key context included.