Response field detailed is no longer guaranteed

What changed

Producer-side tools call this non-breaking. For a consumer it is a null dereference on an unknown future date.

Affects detailed on CreditCategory reachable from 9 operations. Nothing fails at the call; it fails wherever the value is finally used, which is usually somewhere else entirely.

can now be null

Who is affected

Code that reads Plaid's CreditCategory objects, used by 9 Plaid operations.

Before and after

Code that breaks

// response.detailed may now be absent or null
const detailed = response.detailed ?? fallback;

Based on Plaid’s published API specification. How severity is decided.