Update a package on a proposal or booking
Edits a package already on an event, or swaps it for a different one. use_new_or_existing_package decides which: existing, the default, edits the package in place, and new replaces it with the package named by new_event_type_id.
This replaces the package rather than merging into it. Send everything you want the package to keep: existing_title, existing_description_html, override_price, override_ends_at_time and units are all cleared when you leave them out, and taxable goes back to true. Length is the exception: leave length_in_minutes or length_in_days out and the package keeps the length it already has.
Swapping the package drops the old package's add-ons, copies the new one's across, and rebuilds that package's discounts and checklist items.
Required permission: assigned_event_write (when the authenticated user is assigned to the event) or unassigned_event_write (otherwise).
Request
- Base URL: https://api.checkcherry.com
- URL: https://api.checkcherry.com/api/v1/event_bookings/{event_booking_id}
- Auth: none declared. Required headers: Api-Key
Path parameters
Event Booking ID
Headers
Your Integration Key
Request body
Response
package updated
Changes
No recorded changes to this operation across all 2 revisions of this API.