Skip to main content
The Public API follows semantic versioning. Breaking changes ship only in a new major version, and supported versions keep working indefinitely, apart from the exceptions below. Build new integrations against V2.

​
Versions

Each major version has its own base path. The version you call doesn’t change until you change the path.

​
Breaking changes

A change is breaking if it can make a working integration fail or behave differently. Supported versions never get these changes, apart from the exceptions:
  • Removing or renaming an endpoint, field, parameter, or enum value
  • Changing a field’s type or format
  • Adding a required request field, or making an optional one required
  • Rejecting a request that’s accepted today
  • Changing a write’s side effects, such as a delete becoming an archive
  • Changing a list endpoint’s defaults: filters, sort order, or page size
  • Changing authentication or authorization requirements
These changes aren’t breaking and ship without notice:
  • New endpoints, resources, and response headers
  • New optional request fields and parameters
  • New response fields and enum values
  • Changes to the order of response fields, or to the length or format of IDs
Write your integration to ignore fields and enum values it doesn’t recognize, and to treat IDs as opaque strings. Deprecated endpoints and fields keep working in their major version, and DualEntry announces deprecations in advance.

​
Exceptions

A supported version can get a breaking change only to fix one of the issues below. The fix ships to every supported version that serves the endpoint. Security fixes can ship without advance notice. DualEntry announces them on this documentation site.
Last modified on October 30, 2026