Tabba Public API

A REST API that drives invoicing and revenue recognition in Tabba from your own tooling. Authenticate with a Bearer API key, address resources by your own ids, and receive signed webhook events for changes you did not trigger.

API reference Getting started OpenAPI 3.1 spec

There is no sandbox

Tabba does not host a test mode. There are no tpk_test_ keys and no hosted fake-Dinero sandbox. Build against your live integration using a throwaway customer and product — a name like “Test Corp” and a product INTEGRATION-TEST are fine — then delete the records when you are done. See the getting-started guide for the reasoning.

Guides

Getting started

Base URL, first call, and the no-sandbox note.

Authentication

API key format, scope, integration binding, rotation.

external_id and idempotency

Correlating your world with Tabba without holding Tabba UUIDs.

Work registration

Absolute-set hours + completion into the recognition engine.

Issuance and auto-send

Explicit issuance vs the auto-send cron; booked-but-send-failed.

Webhooks

Signed at-least-once events for changes you did not trigger.

Pagination

Cursor iteration and updated_since for incremental sync.

Errors

Envelope, typed codes, rate limits, and versioning policy.

Mint an API key

An admin creates keys in Settings → Developers. Each key is bound to one connected integration and to a read or read_write scope.

Subscribe to webhooks

Signed at-least-once events (invoice.issued, accrual.booked, customer.updated) so a headless integration is never blind to changes it did not trigger.

Versioning

URL-major (/v1) with only additive changes within a major. Your integration will not break under you.