This release adds support for price rounding and display prices across invoicing, reporting, and store order endpoints. Invoice line items now include a 'price_rounding' type to track rounding adjustments, the fees calculator returns rounding amounts, and store order items now expose display prices that reflect customer-facing pricing. These changes enable more accurate price calculations and better alignment between system prices and what customers see.

• GET /invoices – Invoice line items now include the 'price_rounding' type to identify rounding adjustment entries • GET /invoices/{id} – Invoice line items now include the 'price_rounding' type to identify rounding adjustment entries • GET /reports/invoice_line_items.grouped/data – Report rows now include the 'price_rounding' type to identify rounding adjustment line items • GET /reports/invoice_line_items/data – Report rows now include the 'price_rounding' type to identify rounding adjustment line items • POST /store/order_items/{id}/confirm_delivery – Now requires and returns 'price_for_display' to show the customer-facing price when confirming delivery • POST /fees_calculator – Fee calculations now return the 'rounding_amount' applied to the total • POST /fees_calculator/bulk – Bulk fee calculations now return the 'rounding_amount' for each calculation result • GET /reports/store_orders/data – Reports can now include 'total_price_for_display' column to show customer-facing order totals • POST /reports/store_orders/export – Exports can now include 'total_price_for_display' column to show customer-facing order totals • GET /store/order_items – Order items now include 'price_for_display' to show the customer-facing price for each item • POST /store/order_items – Created order items now return 'price_for_display' to show the customer-facing price • PATCH /store/order_items/{id} – Updated order items now return 'price_for_display' to show the customer-facing price • PUT /store/order_items/{id} – Updated order items now return 'price_for_display' to show the customer-facing price

GET /invoices

• added the new price_rounding enum value to the results/items/line_items/items/type response property for the response status 200 (media type: application/json)

View updated docs

GET /invoices/{id}

• added the new price_rounding enum value to the line_items/items/type response property for the response status 200 (media type: application/json)

View updated docs

GET /reports/invoice_line_items.grouped/data

• added the new price_rounding enum value to the rows/items/type response property for the response status 200

View updated docs

GET /reports/invoice_line_items/data

• added the new price_rounding enum value to the rows/items/type response property for the response status 200

View updated docs

POST /store/order_items/{id}/confirm_delivery

• added the new required request property price_for_display (media type: application/json)
• added the required property price_for_display to the response with the 200 status (media type: application/json)

View updated docs

POST /fees_calculator

• added the required property rounding_amount to the response with the 200 status (media type: application/json)

View updated docs

POST /fees_calculator/bulk

• added the required property results/items/rounding_amount to the response with the 200 status (media type: application/json)

View updated docs

GET /reports/store_orders/data

• added the enum value total_price_for_display to the property items/ of the query request parameter columns
• added the optional property rows/items/total_price_for_display to the response with the 200 status

View updated docs

POST /reports/store_orders/export

• added the new total_price_for_display enum value to the request property columns/items/ (media type: application/json)

View updated docs

GET /store/order_items

• added the required property results/items/price_for_display to the response with the 200 status (media type: application/json)

View updated docs

POST /store/order_items

• added the required property price_for_display to the response with the 201 status (media type: application/json)

View updated docs

PATCH /store/order_items/{id}

• added the required property price_for_display to the response with the 200 status (media type: application/json)

View updated docs

PUT /store/order_items/{id}

• added the required property price_for_display to the response with the 200 status (media type: application/json)

View updated docs

This release adds a new endpoint for marking push notifications as read and introduces a CRM setting to control how far back deal statuses can be moved. These changes give developers more control over notification management and deal status workflows.

• GET /crm/settings now returns earliest_backward_transition_status, allowing you to see the minimum status a deal can be moved back to in your CRM pipeline.
• PATCH /crm/settings now accepts earliest_backward_transition_status, enabling you to configure restrictions on how far backward deals can be moved in your status workflow.
• POST /push_notifications/mark_send_read is a new endpoint that allows you to programmatically mark push notifications as read.

GET /crm/settings

• added the optional property earliest_backward_transition_status to the response with the 200 status (media type: application/json)

View updated docs

PATCH /crm/settings

• added the new optional request property earliest_backward_transition_status (media type: application/json)
• added the optional property earliest_backward_transition_status to the response with the 200 status (media type: application/json)

View updated docs

POST /push_notifications/mark_send_read

• endpoint added

View updated docs

This release enhances template variable metadata across communication and gift card endpoints by adding fields to indicate which variables are required or part of a required group. Additionally, the customer reports endpoint now includes email addresses for family managers, enabling better contact management and reporting capabilities.

• GET /communication/notification_types/membership_penalty — Template variables now indicate which fields are required and which belong to required groups, helping developers properly populate notification templates.
• GET /communication/notification_types/missing_forms_waivers/metadata — Template variables now indicate which fields are required and which belong to required groups, helping developers properly populate notification templates.
• GET /gift_cards/config/metadata — Template variables now indicate which fields are required and which belong to required groups, helping developers properly populate gift card configuration templates.
• GET /reports/customers/data — Customer report data now includes email addresses for family managers, enabling direct communication and enhanced contact management.

GET /communication/notification_types/membership_penalty

• added the optional property template_variables/items/required to the response with the 200 status (media type: application/json)
• added the optional property template_variables/items/required_group to the response with the 200 status (media type: application/json)

View updated docs

GET /communication/notification_types/missing_forms_waivers/metadata

• added the optional property template_variables/items/required to the response with the 200 status (media type: application/json)
• added the optional property template_variables/items/required_group to the response with the 200 status (media type: application/json)

View updated docs

GET /gift_cards/config/metadata

• added the optional property template_variables/items/required to the response with the 200 status (media type: application/json)
• added the optional property template_variables/items/required_group to the response with the 200 status (media type: application/json)

View updated docs

GET /reports/customers/data

• added the required property rows/items/family/managers/items/email to the response with the 200 status

View updated docs

This release improves gift card endpoints by standardizing ID parameters to accept strings, adds comprehensive error response documentation (401, 403, 404, 429), and removes legacy expand/fields query parameters. Additionally, marketing suite configuration now supports managing Teamup invite preferences with a new PATCH endpoint for partial updates.

• GET /gift_cards/{id} now accepts string-based gift card IDs and documents authentication, authorization, not found, and rate limit error responses. The expand and fields query parameters have been removed.
• POST /gift_cards/{id}/redeem now accepts string-based gift card IDs and documents validation, authentication, authorization, not found, and rate limit error responses. The expand and fields query parameters have been removed.
• GET /integrations/marketing_suite/config now returns whether Teamup invitations are sent, allowing clients to view this configuration setting.
• PATCH /integrations/marketing_suite/config enables clients to update marketing suite configuration settings, including Teamup invite preferences, without replacing the entire configuration.

GET /gift_cards/{id}

• deleted the query request parameter expand
• deleted the query request parameter fields
• for the path request parameter id, the type was widened from integer to string
• added the non-success response with the status 401
• added the non-success response with the status 403
• added the non-success response with the status 404
• added the non-success response with the status 429

View updated docs

POST /gift_cards/{id}/redeem

• deleted the query request parameter expand
• deleted the query request parameter fields
• for the path request parameter id, the type was widened from integer to string
• added the non-success response with the status 400
• added the non-success response with the status 401
• added the non-success response with the status 403
• added the non-success response with the status 404
• added the non-success response with the status 429

View updated docs

GET /integrations/marketing_suite/config

• added the optional property send_teamup_invite to the response with the 200 status (media type: application/json)

View updated docs

PATCH /integrations/marketing_suite/config

• endpoint added

View updated docs

This release introduces comprehensive push notification management capabilities to the API, allowing developers to retrieve, mark as read, and delete push notifications. Additionally, customer notification preferences have been extended to include push notification settings, giving users granular control over how they receive notifications.

• GET /customers/{id}/notification_preferences – Retrieve customer notification preferences, now including a push_enabled flag to determine whether push notifications are enabled for the customer.
• PATCH /customers/{id}/notification_preferences/{notification_preference_id} – Update customer notification preferences with the ability to enable or disable push notifications via the new push_enabled field.
• GET /push_notifications – Retrieve a list of push notifications for the authenticated user.
• POST /push_notifications/mark_all_read – Mark all push notifications as read in a single operation.
• DELETE /push_notifications/{id} – Delete a specific push notification.
• POST /push_notifications/{id}/mark_read – Mark a specific push notification as read.

GET /customers/{id}/notification_preferences

• the response property id became nullable for the status 200 (media type: application/json)
• added the optional property push_enabled to the response with the 200 status (media type: application/json)

View updated docs

PATCH /customers/{id}/notification_preferences/{notification_preference_id}

• the response property id became nullable for the status 200 (media type: application/json)
• added the new optional request property push_enabled (media type: application/json)
• removed the pattern ^\d+$ from the path request parameter notification_preference_id
• added the optional property push_enabled to the response with the 200 status (media type: application/json)

View updated docs

GET /push_notifications

• endpoint added

View updated docs

POST /push_notifications/mark_all_read

• endpoint added

View updated docs

DELETE /push_notifications/{id}

• endpoint added

View updated docs

POST /push_notifications/{id}/mark_read

• endpoint added

View updated docs

This release introduces comprehensive embed widget management capabilities, allowing developers to programmatically create, retrieve, update, and delete calendar embed widgets through the API. Additionally, membership filtering has been enhanced to support course registration scenarios.

• GET /embed/bootstrap – Retrieve bootstrap configuration data for calendar embeds
• GET /embed_widgets – List all embed widgets configured for your calendar
• POST /embed_widgets – Create new embed widgets to display your calendar on external websites
• GET /embed_widgets/{id} – Retrieve details of a specific embed widget
• PUT /embed_widgets/{id} – Update an existing embed widget configuration
• PATCH /embed_widgets/{id} – Partially update specific fields of an embed widget
• DELETE /embed_widgets/{id} – Delete an embed widget
• GET /memberships – Filter memberships by those that permit registration for a specific course

GET /embed/bootstrap

• endpoint added

View updated docs

GET /embed_widgets

• endpoint added

View updated docs

POST /embed_widgets

• endpoint added

View updated docs

DELETE /embed_widgets/{id}

• endpoint added

View updated docs

GET /embed_widgets/{id}

• endpoint added

View updated docs

PATCH /embed_widgets/{id}

• endpoint added

View updated docs

PUT /embed_widgets/{id}

• endpoint added

View updated docs

GET /memberships

• added the new optional query request parameter permits_registration_for_course

View updated docs

GET /checkouts

• added the optional property results/items/checkout_items/items/oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property results/items/checkout_items/items/oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property results/items/checkout_items/items/oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)

View updated docs

POST /checkouts

• added the optional property checkout_items/items/oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership to the response with the 201 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership to the response with the 201 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership to the response with the 201 status (media type: application/json)

View updated docs

POST /checkouts/preview-discount-code

• added the new optional request property item/oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership (media type: application/json)
• added the new optional request property item/oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership (media type: application/json)
• added the new optional request property item/oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership (media type: application/json)

View updated docs

GET /checkouts/{id}

• added the optional property checkout_items/items/oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)

View updated docs

PATCH /checkouts/{id}

• added the optional property checkout_items/items/oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)

View updated docs

PUT /checkouts/{id}

• added the optional property checkout_items/items/oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)

View updated docs

POST /checkouts/{id}/add_item

• added the new optional request property oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership (media type: application/json)
• added the new optional request property oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership (media type: application/json)
• added the new optional request property oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)

View updated docs

POST /checkouts/{id}/cancel

• added the optional property checkout_items/items/oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property checkout_items/items/oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)

View updated docs

GET /checkouts/{id}/items/{item_id}/

• added the optional property oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)

View updated docs

POST /checkouts/{id}/items/{item_id}/price/

• added the optional property oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)

View updated docs

POST /checkouts/{id}/items/{item_id}/quantity/

• added the optional property oneOf[subschema #13: PrepaidMembershipCheckoutItem -> subschema #12: PrepaidMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property oneOf[subschema #18: PackMembershipCheckoutItem -> subschema #2: PackMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)
• added the optional property oneOf[subschema #9: RecurringMembershipCheckoutItem -> subschema #16: RecurringMembershipCheckoutItem]/renew_from_customer_membership to the response with the 200 status (media type: application/json)

View updated docs

GET /communication/push_settings/class_reminders

• endpoint added

View updated docs

POST /communication/push_settings/class_reminders

• endpoint added

View updated docs

DELETE /communication/push_settings/class_reminders/{id}

• endpoint added

View updated docs

GET /communication/push_settings/class_reminders/{id}

• endpoint added

View updated docs

PATCH /communication/push_settings/class_reminders/{id}

• endpoint added

View updated docs

PUT /communication/push_settings/class_reminders/{id}

• endpoint added

View updated docs

GET /customer_memberships

• added the required property results/items/renew_from to the response with the 200 status (media type: application/json)

View updated docs

POST /customer_memberships

• added the required property renew_from to the response with the 201 status (media type: application/json)

View updated docs

POST /customer_memberships/bulk_edit_prices

• added the required property renew_from to the response with the 200 status (media type: application/json)

View updated docs

GET /customer_memberships/{id}

• added the required property renew_from to the response with the 200 status (media type: application/json)

View updated docs

POST /customer_memberships/{id}/cancel

• added the required property renew_from to the response with the 200 status (media type: application/json)

View updated docs

GET /invoices

• added the enum value -id to the property items/ of the query request parameter sort
• added the enum value id to the property items/ of the query request parameter sort

View updated docs

This release introduces read-only access control for machine-to-machine tokens and exposes plan change options across customer membership endpoints. Developers can now create or update M2M tokens with read-only permissions to limit API access, and retrieve detailed plan change options when working with customer memberships.

• POST /auth/m2m_tokens now supports creating machine-to-machine tokens with read-only access restrictions
• PATCH /auth/m2m_tokens/{id} now allows updating tokens to read-only mode and returns the read-only status in responses
• PUT /auth/m2m_tokens/{id} now supports setting read-only access when fully replacing a token
• GET /customer_memberships now returns available plan change options for each membership in the list
• POST /customer_memberships now includes plan change options in the response when creating a new membership
• POST /customer_memberships/bulk_edit_prices now returns plan change options after bulk price updates
• GET /customer_memberships/{id} now provides plan change options when retrieving a specific membership
• POST /customer_memberships/{id}/cancel now returns plan change options when canceling a membership

POST /auth/m2m_tokens

• added the new optional request property is_read_only (media type: application/json)

View updated docs

PATCH /auth/m2m_tokens/{id}

• added the new optional request property is_read_only (media type: application/json)
• added the required property is_read_only to the response with the 200 status (media type: application/json)

View updated docs

PUT /auth/m2m_tokens/{id}

• added the new optional request property is_read_only (media type: application/json)

View updated docs

GET /customer_memberships

• added the optional property results/items/plan_change_options to the response with the 200 status (media type: application/json)

View updated docs

POST /customer_memberships

• added the optional property plan_change_options to the response with the 201 status (media type: application/json)

View updated docs

POST /customer_memberships/bulk_edit_prices

• added the optional property plan_change_options to the response with the 200 status (media type: application/json)

View updated docs

GET /customer_memberships/{id}

• added the optional property plan_change_options to the response with the 200 status (media type: application/json)

View updated docs

POST /customer_memberships/{id}/cancel

• added the optional property plan_change_options to the response with the 200 status (media type: application/json)

View updated docs

This release fixes a typo in the day-of-week enum value across multiple endpoints, correcting 'staturday' to 'saturday'. Additionally, push notification settings now support configuration for missing forms and waivers notifications.

• GET /membership_payment_plans – corrected the day-of-week enum value for fixed billing days from 'staturday' to 'saturday'
• POST /membership_payment_plans – corrected the day-of-week enum value for fixed billing days from 'staturday' to 'saturday' in both requests and responses
• GET /membership_payment_plans/{id} – corrected the day-of-week enum value for fixed billing days from 'staturday' to 'saturday'
• PATCH /membership_payment_plans/{id} – corrected the day-of-week enum value for fixed billing days from 'staturday' to 'saturday'
• PUT /membership_payment_plans/{id} – corrected the day-of-week enum value for fixed billing days from 'staturday' to 'saturday'
• GET /recurring_reservations – corrected the day-of-week enum value from 'staturday' to 'saturday'
• GET /recurring_reservations/{id} – corrected the day-of-week enum value from 'staturday' to 'saturday'
• PATCH /recurring_reservations/{id} – corrected the day-of-week enum value from 'staturday' to 'saturday'
• GET /registration_options – corrected the day-of-week enum value in time slots from 'staturday' to 'saturday'
• GET /reports/classes.grouped/data – corrected the day-of-week filter value from 'staturday' to 'saturday'
• POST /reports/classes.grouped/export – corrected the day-of-week filter value from 'staturday' to 'saturday'
• GET /reports/classes/data – corrected the day-of-week filter value from 'staturday' to 'saturday'
• POST /reports/classes/export – corrected the day-of-week filter value from 'staturday' to 'saturday'
• GET /communication/push_settings – now includes settings for missing forms and waivers notifications
• PATCH /communication/push_settings – now supports configuring push notifications for missing forms and waivers

GET /membership_payment_plans

• added the new saturday enum value to the results/items/fixed_billing_day_of_week response property for the response status 200 (media type: application/json)
• removed the staturday enum value from the results/items/fixed_billing_day_of_week response property for the response status 200 (media type: application/json)

View updated docs

POST /membership_payment_plans

• removed the enum value staturday of the request property fixed_billing_day_of_week (media type: application/json)
• added the new saturday enum value to the fixed_billing_day_of_week response property for the response status 201 (media type: application/json)
• added the new saturday enum value to the request property fixed_billing_day_of_week (media type: application/json)
• removed the staturday enum value from the fixed_billing_day_of_week response property for the response status 201 (media type: application/json)

View updated docs

GET /membership_payment_plans/{id}

• added the new saturday enum value to the fixed_billing_day_of_week response property for the response status 200 (media type: application/json)
• removed the staturday enum value from the fixed_billing_day_of_week response property for the response status 200 (media type: application/json)

View updated docs

PATCH /membership_payment_plans/{id}

• added the new saturday enum value to the fixed_billing_day_of_week response property for the response status 200 (media type: application/json)
• removed the staturday enum value from the fixed_billing_day_of_week response property for the response status 200 (media type: application/json)

View updated docs

PUT /membership_payment_plans/{id}

• added the new saturday enum value to the fixed_billing_day_of_week response property for the response status 200 (media type: application/json)
• removed the staturday enum value from the fixed_billing_day_of_week response property for the response status 200 (media type: application/json)

View updated docs

GET /recurring_reservations

• added the new saturday enum value to the results/items/day response property for the response status 200 (media type: application/json)
• removed the staturday enum value from the results/items/day response property for the response status 200 (media type: application/json)

View updated docs

GET /recurring_reservations/{id}

• added the new saturday enum value to the day response property for the response status 200 (media type: application/json)
• removed the staturday enum value from the day response property for the response status 200 (media type: application/json)

View updated docs

PATCH /recurring_reservations/{id}

• added the new saturday enum value to the day response property for the response status 200 (media type: application/json)
• removed the staturday enum value from the day response property for the response status 200 (media type: application/json)

View updated docs

GET /registration_options

• added the new saturday enum value to the results/items/time_slots/items/day response property for the response status 200 (media type: application/json)
• removed the staturday enum value from the results/items/time_slots/items/day response property for the response status 200 (media type: application/json)

View updated docs

GET /reports/classes.grouped/data

• removed the enum value staturday from the property items/ of the query request parameter day_of_week
• added the enum value saturday to the property items/ of the query request parameter day_of_week

View updated docs

POST /reports/classes.grouped/export

• removed the enum value staturday of the request property day_of_week/items/ (media type: application/json)
• added the new saturday enum value to the request property day_of_week/items/ (media type: application/json)

View updated docs

GET /reports/classes/data

• removed the enum value staturday from the property items/ of the query request parameter day_of_week
• added the enum value saturday to the property items/ of the query request parameter day_of_week

View updated docs

POST /reports/classes/export

• removed the enum value staturday of the request property day_of_week/items/ (media type: application/json)
• added the new saturday enum value to the request property day_of_week/items/ (media type: application/json)

View updated docs

GET /communication/push_settings

• added the required property missing_forms_and_waivers to the response with the 200 status (media type: application/json)

View updated docs

PATCH /communication/push_settings

• added the new optional request property missing_forms_and_waivers (media type: application/json)
• added the required property missing_forms_and_waivers to the response with the 200 status (media type: application/json)

View updated docs

This release introduces course series support, enabling clients to group related course sessions together and retrieve series-level metadata. Two new endpoints for listing and retrieving course series have been added, and existing course session endpoints now include series identifiers and session numbering. Additionally, BoxMate integration support has been removed.

• GET /course_sessions — Retrieve course sessions with new series filtering capability via the series query parameter. Responses now include series identifiers and session numbering (session_number and session_total) to show each session's position within its parent series. Attendance and occupancy fields are now optional.
• GET /course_sessions/{id} — Retrieve individual course sessions with new series metadata, including the series identifier and session numbering information. Attendance and occupancy fields are now optional.
• GET /course_series — New endpoint to list all course series, enabling clients to browse and discover available course series.
• GET /course_series/{id} — New endpoint to retrieve detailed information about a specific course series by its identifier.
• GET /integrations/ — BoxMate integration is no longer supported and has been removed from available integrations.

GET /course_sessions

• the response property results/items/attending_count became optional for the status 200 (media type: application/json)
• the response property results/items/max_occupancy became optional for the status 200 (media type: application/json)
• added the new optional query request parameter series
• added the required property results/items/series to the response with the 200 status (media type: application/json)
• added the required property results/items/session_number to the response with the 200 status (media type: application/json)
• added the required property results/items/session_total to the response with the 200 status (media type: application/json)

View updated docs

GET /course_sessions/{id}

• the response property attending_count became optional for the status 200 (media type: application/json)
• the response property max_occupancy became optional for the status 200 (media type: application/json)
• added the required property series to the response with the 200 status (media type: application/json)
• added the required property session_number to the response with the 200 status (media type: application/json)
• added the required property session_total to the response with the 200 status (media type: application/json)

View updated docs

GET /course_series

• endpoint added

View updated docs

GET /course_series/{id}

• endpoint added

View updated docs

GET /integrations/

• removed subschema #5: BoxMate from the items/ response property oneOf list for the response status results (media type: application/json)

View updated docs