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.

Base URL

All requests use https://api.dualentry.com, including requests from a sandbox organization, if you’re testing an integration before pointing it at production. Your API key is scoped to the organization it was issued from, so there’s no separate host to configure; only the key changes between a sandbox and a production integration.
All API requests use HTTPS. The API accepts and returns JSON-formatted data.

Next steps

  • Authentication: key statuses, roles, and how authorization failures are reported.
  • Core Concepts: the mechanics every integration needs to get right, including rate limits, pagination, and idempotent writes.
  • Versioning: which version to build against and what counts as a breaking change.
  • API Reference: every endpoint, request and response schema, and parameter.
If you’re building a production integration for the partner program rather than a one-off script, see How Custom Integrations Work.
Last modified on September 23, 2026