Adds risk requirements to the Capabilities APIBreaking changes

What’s new

Adds risk requirements to the requirements hash of the Capability object.

Previously, risk requirements only appeared in the requirements and future_requirements hashes of the Account object. In the Accounts v1 API, those hashes don’t identify the capabilities that a particular requirement affects.

Why is this a breaking change?

The Capability object’s requirements hash can now contain risk-related requirements. If your integration assumes that it doesn’t include them, you might need to update your code.

Impact

When using the Accounts v1 API, you can now programmatically identify capabilities that are or can be affected by risk requirements by using the Capabilities API.

If you use the Accounts v2 API, you don’t need to use the Capabilities API. In Accounts v2, each entry in the requirements and future_requirements hashes includes an impact.restricts_capabilities array listing the capabilities affected by that requirement.

Upgrade