Theme Parks API Changelog
4 min
\<font color="#b6c7cb">\</font> topic type concept purpose record contractual and behavioral changes to the theme parks api over time audience api integrators and client developers maintaining or upgrading integrations applies to the theme parks api and its published openapi reference does not apply to other industry specific apis or i nternal implementation changes that do not affect the public api contract this changelog documents contractual and behavioral changes to the theme parks api it is intended to help integrators understand how the api has evolved and assess the impact of changes on existing integrations the openapi reference remains the single source of truth for the current api contract this changelog provides historical context and impact classification for changes reflected in the reference how to read this changelog each entry is listed in reverse chronological order and classified by impact level type meaning client action breaking a change that may require code changes or integration updates classifications removed, changed required update backward compatible a change that does not break existing integrations classifications added, changed, deprecated optional update behavioral contract unchanged, behavior changed classification changed review documentation a clarification or correction with no contract or behavior change classification clarified none when a field or behavior is deprecated, the changelog records the deprecation date the recommended replacement (if applicable) whether removal is planned for a future release changelog entries version 1 4 ( expanded authentication options) type backward compatible added added support for oauth 2 0 (client credentials) authentication in addition to basic authentication version 1 3 (payment schema field relocation) type breaking changed moved ispaymentrecurring from the paymentmethods block to the payment block version 1 2 (authentication and payment enhancements) type breaking removed removed support for jwt authentication custom authentication type backward compatible added added seccard as a payment type for corporate issued payments used within secure payment portals added isrecurring field to the paymentmethods object for subscription handling changed moved accountstatus and hashedpassword to the root level version 1 1 (authentication and token support) type backward compatible added added authenticationmethod field added cardtoken field to the paymentmethods block