GuidesAPI ReferenceChangelog
HomeGuidesAPI ReferenceChangelog
GuidesAPI ReferenceChangelogLog In
Back to All

Revel 2.66 API Updates

over 3 years ago by McPherson White

Welcome to the 2.66 Revel API changelog!

In Revel 2.66 we've made important updates to orders, gift and loyalty endpoints. We've also added support for our new curbside pickup dining option and enhanced our online ordering documentation.

Please review these updates in order to test and update your integrations accordingly.

You can learn more about the general 2.66 release here.

Added Resources

  • We’ve updated our documentation for the Weborders API to adhere with OAS standards.

Removed Resources

  • We’ve removed the OrderAllInOne resource from the Orders suite, as we plan to deprecate the endpoint going forward.
  • We’ve removed the entirety of the Gift suite, as we plan to deprecate the endpoint going forward. This includes the following resources: GiftCard and GiftCardLog.
  • We’ve removed the entirety of the Loyalty suite, as we plan to deprecate the endpoint going forward. This includes the following resources: LoyaltyTier, LoyaltyTierRule, RewardCardLog and RewardsCard.

Modified Resources

  • The Order resource has been updated to accommodate pickup ordering with a new available value (8) added to the dining_option field.
  • pickup_data is a new object available for orders whose dining_option = 8. It contains the following fields used to support the pickup experience: email, status, call_name, pickup_type, phone_number, vehicle_make, vehicle_type, vehicle_color, customer_arrived and send_confirmation.
  • For more information on the configuration required to support the new pickup dining option, please reference our support knowledge base.

Planned Deprecation

  • We have begun deprecating the OrderAllInOne resource as well as the entirety of the Gift and Loyalty API suites (as well as endpoints and methods contained therein). These resources will no longer be available for new third-party integrations. If you are still using them, please reach out to [email protected] for information on more suitable alternatives.