Developer workstation with code editor and keyboard

Developer API

Integration guidance before open endpoints

The developer surface prepares teams for auth, tenant-aware integrations, event handling, guided submission, and country-governed accounting workflows before broader public API release.

Open Docs Open Help Vietnam law hub

Public Direction

What the developer surface is preparing now

Auth and tenancy

Identity, tenant scoping, role-aware access, and evidence-safe session behavior.

Document and intake flows

File intake, validation, queueing, review states, and record lineage for accounting workflows.

Events and webhooks

Status changes, review outcomes, guided submission progress, export package handoff, and auditable event delivery are part of the roadmap.

Country-aware integrations

Every integration surface stays country-aware and opens only with approved country-pack scope, the right law hub, and synchronized docs/help/API truth.

Release Posture

The API surface opens in controlled stages

Publish terminology, lifecycle, and integration guidance first.
Publish auth, evidence, and tenant assumptions before broad endpoint disclosure.
Align developer docs with the same product truth as docs and help.
Open partner and pilot integration routes only after release governance approves them.
Keep country routing and switcher truth aligned so no API page implies a country is already live before country pack, law hub, docs/help/API sync, legal approval, and routing gate approval.
Keep changelog, versioning, and support boundaries visible once the surface expands.

Abstract data visualization and integration planning

Developer Guardrails

What stays locked on the public API surface

No client-side secrets

Secret material, long-lived tokens, and privileged credentials must never appear in client code or public snippets.

Versioned contracts

Shared schemas and integration contracts need documented change posture before wider partner use.

Country-safe scope

Integration claims must match the approved country-pack, filing mode, and support reality for that jurisdiction. For Vietnam today, the public-safe path stops at guided submission and export package.

No ungated country hosts

vn.aiaccountingloop.com is the first governed country host. No other country host, switcher entry, or automatic routing path belongs on the API surface before the full gate is active.

Audit and evidence first

Observable event history and evidence-safe workflows stay ahead of convenience features.

Public API pricing and broad endpoint disclosure are still private as of April 13, 2026. This page establishes the governed developer direction, not a public commercial package.

The first governed country-law lane is Vietnam at /countries/vn/, paired with vn.aiaccountingloop.com as the first governed country host.

Control Snapshot

Developer direction stays inside the live Team 1 control state

Public filing posture

guided submission only

Developer-facing wording stays inside the live public filing boundary.

Public-safe path

EXPORT_PACKAGE

No public API direction may imply a stronger submission path today.

Active decisions

Developer direction follows only current Team 1 decisions in force.

Latest Team 1 sync snapshot: 2026-04-13 16:00:30 +0700.