Revel 2.59 API Updates
over 5 years ago by Sujin Headrick
Welcome to the 2.59 Revel API changelog!
In Revel 2.59 we've made important updates to products, orders, establishments, and combos. We've also added support for pass through service fees, pre-discount service fees, and KDS redirects.
Please review these updates and update your applications accordingly.
You can learn more about the general 2.59 release here.
Modified Resources
- We've added
apply_to,pass_through_fee_type, andinclude_employee_pass_through_fee_infields in theAppliedServiceFeeresource to support pass through service fees. Thepost_taxfield no longer has a default value. - The
ComboProductSetnow includes anis_upsellfield, which supports boolean values. Thesurchargefield is now read-only and may be blank. - We've removed the
master_discount_idfield from theDiscountresource. - The
Establishmentresource now includes aRUIDfield. - We've added
version,customer_address_distance, andvirtual_datafields to theOrderandOrderAllInOneresources to support adding an address's distance and internal reporting. - The
combo_typefield in theOrderTyperesource is now nullable. - We've added a
kds_redirectfield to thePosStationresource to support redirecting to a new KDS. This field accepts boolean values. - We've removed the
rrpandis_localfields from theProduct,ProductPurchase, andViewPurchaseOrderProductresources. Also, we've added theproduct_price_in_comboandsurchargefields. - We've removed the
rrpfield from theProductPriceLifeCycleActionresource. - We've added a
product_modifier_classfield to theProductModifierresource. You can also filter byproduct_modifier_class. - The
ServiceFeeresource now includesapply_to,pass_through_fee_type,include_employee_pass_through_fee_in,use_distance,max_distance, andmin_distancefields to support pass through service fees and service fees by distance. Also, theapply_post_taxfield no longer includes a default value. - In the
Userresource, we've added fields forRUID,is_reseller,auth0_id,is_bill_to, andis_sold_toAlso, thehas_enterprise_accessfield is no longer available.
Changes and Bug Fixes
- We've added a
tip_sharesfield to the Sales Summary JSON report. - In the Online Ordering suite, the
barcodeis now an accepted value formodifieritems, along withmodifier_id.
"modifieritems": [
{
"modifier": "2129714",
"modifier_cost": 0,
"modifier_price": 1,
"qty": 1,
"qty_type": 0,
"admin_mod_key": ""
}
]
- When using a custom transaction ID on the POS for receiptless returns, the custom transaction ID is captured as the
transaction_idin thePaymentresource. - The
activefield in theVendorEstablishmentfield is now set toTrueby default in POST requests. - Duplicate
barcodevalues are no longer allowed forInventoryUnitPOST or PATCH requests. - The
rolesfield is only available as a filter forEmployeeGET requests.
Planned Deprecation
We have begun deprecating the Brand, Device, KitchenView, CustomerHistory, RewardsCardv3, and InventoryStockAmount resources. These resources will not be available for third-party developers after our upcoming 2.62 release (tentatively Q2 2020). We discourage you from using these resources. If you are still using them, please reach out to [email protected].