Skip to main content
Make your first authenticated call to the DualEntry Public API in under five minutes. By the end, you’ll have a working API key and a successful response from a live endpoint.

Get an API key

Ask your DualEntry administrator to generate an API key for you, or see Give an integration access if you’re the administrator. Every request authenticates with this key in the X-API-KEY header. There’s no OAuth flow or token exchange to set up.

Make your first request

Request the invoices collection. Replace your_api_key_here with your real key.
A successful response returns a 200 status with a paginated list of invoices:
A 403 here almost always means the key is missing a role. See Errors for the full list of failure responses.

What you can build

  • Financial transactions: create and manage invoices, bills, payments, journal entries, and purchase orders.
  • Customer and vendor management: maintain customer and vendor records with complete contact and payment term information.
  • Chart of Accounts: configure and manage your accounting structure with accounts, items, and classifications.
  • Automation: set up recurring transactions for subscriptions, rent, and other regular financial activities.
  • Bank Connections inbound: push bank transactions from your own systems into DualEntry with /public/v2/bank-connections/. See Bank Connections inbound.

Base URLs

The API is available in production and a separate development environment, each with its own base URL.
All API requests use HTTPS. The API accepts and returns JSON-formatted data.

Next steps

  • Introduction: API versioning, resource coverage, and what V2 adds over V1.
  • Authentication: key statuses, roles, and how authorization failures are reported.
  • API Reference: every endpoint, request and response schema, and parameter.
Last modified on August 28, 2026