Skip to main content
DualEntry’s Public API follows semantic versioning. Additive changes, such as new fields, endpoints, and resources, ship continuously without a version bump. A breaking change only ever ships as a new major version, and a superseded major version keeps working indefinitely: you’re never required to migrate on a deadline. V2 is the current, stable version. Build new integrations against it. Versions marked alpha are the exception to the guarantees above: they can change, including breaking changes, without notice, and shouldn’t be used in production. See V3 (Alpha). Moving to a new major version is mechanically just a base URL change (for example, /public/v1/ to /public/v2/). Verify request and response shapes for the resources you use via the API Reference, since coverage and behavior aren’t guaranteed identical across versions.
Last modified on September 23, 2026