How would you release this API change without breaking supported consumers?

Instruction: Build a compatibility and deployment plan from the supplied consumer behaviors, including rollback.

Context:

A fictional version-1 payment-status API returns {"id":"P1","status":"complete"}. Supported consumer A version 3 accepts extra fields but recognizes only pending and complete. Supported consumer B version 1 rejects unknown response fields and uses the same status enum. B cannot be upgraded for 30 days. A provider proposal adds processed_at and replaces complete with settled on the existing v1 route. Its broad schema test permits both, so the provider suite passes. Existing supported consumers and their previous rollback versions are available for contract testing.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

I would block that change on the existing v1 route because both changes violate known consumer assumptions. A rejects the new status, and B also rejects the added field...

Upgrade to view official answer

Related Questions