Service API resources
The public Service API (api.trancent.dev/v1) is the integration surface
for developers building backend systems against Trancent. Organizations and
ledgers are created in the Trancent dashboard; the
Service API gives you programmatic read and write access to ledger data.
Every request to /v1/* must be authenticated with an
API key and HMAC-SHA256 signature.
| Resource | Path pattern | Description |
|---|---|---|
| Organizations | /v1/organizations | Create and list organizations. Returns org IDs used in every other call. |
| Ledgers | /v1/organizations/{orgId}/ledgers | Create a ledger (double-entry book) scoped to an organization. Each ledger is |
| fully isolated and holds journal entries, balances, and period closes. | ||
| Journal entries | /v1/ledgers/{ledgerId}/journal-entries | Post new entries, list by query, and reverse existing entries. |
Lines within an entry may use different currencies; the system enforces
functional‑amount sum‑zero. |
| Period closes | /v1/ledgers/{ledgerId}/period-closes | Close an accounting period, producing an immutable record and a Merkle root
for audit integrity. |
| Error responses | — | All endpoints return RFC 9457 problem details on
failure.
See each resource page for full request/response details: Authentication · Ledgers · Journal Entries · Period Closes · Errors