Plans now link to individual products, with several fields moving to the product resourceBreaking changes
What’s new
Each Plan object is now linked to a Product object with type=service. This change moves the Plan object statement_ and name attributes to Product objects. Additionally, Plan objects now have a nickname attribute. Creating a plan now requires passing a product attribute to POST /v1/plans. This can be either an existing product ID or a dictionary of product fields, so that you can continue to create plans without separately creating products.
Impact
This change introduces a new relationship between Plan and Product objects, moving certain attributes to the Product object and adding a nickname to plans. You now need to specify a product when creating plans, either by referencing an existing product or providing product details. This modification enhances the flexibility and organization of subscription-related data, but requires updates to plan creation processes.