Accounts v2 now always returns the responsibilities field when the defaults field is includedBreaking changes
What’s new
The defaults.responsibilities field is now always returned in the Accounts v2 object if you specify defaults in the include field. This is a breaking change for users on the existing public preview for Accounts v2, which became available in our GA channel as of 2025-12-15.clover.
Why is this a breaking change?
The defaults. field is returned even when responsibilities.fees_collector and responsibilities.losses_collector are null. If your existing integration doesn’t expect this field in API responses, you must use the new object structure to prevent validation errors.
Impact
Previously, the responsibilities.requirements_collector field wasn’t returned unless fees_ and losses_ were present in the response.
You must update your integration to expect the defaults. field, even if you didn’t set fees_ and losses_ when creating or updating the account. Make sure your integration correctly handles fees_ and losses_ when their values are null.