API Changelog
Back to All

API Change Log – April 30, 2024

over 1 year ago by Meghana Rangaraju

Updates for this release.

Fitness

  • API Endpoint: {api_url}/v1/classes/sessions
  • Scenario: This API has been enhanced to include the breakdown of categories and subcategories with the use of the expand parameter ‘categories’ when retrieving the list of active class sessions.
  • Earlier behavior: This API couldn’t retrieve categories and subcategories separately.
  • New behavior: Retrieves details of active class sessions with the breakdown of categories and subcategories with the use of the expand parameter ‘categories’ when retrieving the list of active class sessions.
  • API documentation link:

Fitness

  • API Endpoint: {api_url}/v1/workshops/schedules
  • Scenario: This API has been created to retrieve the list of active schedules of workshop sessions in multiple centers.
  • Earlier behavior: New API. No earlier behavior.
  • New behavior: Retrieves the list of active schedules of workshop sessions in multiple centers.
  • API documentation link:

Admin

  • API Endpoint: {api_url}/v1/organizations/center_settings
  • Scenario: This API retrieves all the center settings of an organization in JSON format.
  • Earlier behavior: New API. No earlier behavior.
  • New behavior: Retrieves all the center settings of an organization in JSON format
  • API documentation link:

Notifications

  • API Endpoint: {api_url}/v1/notifications/unsubscribe
  • Scenario: This API has been created to unsubscribe the guest from marketing messages. Depending on the input provided to the API, it unsubscribes the guest from email, text, or both notifications.
  • Earlier behavior: New API. No earlier behavior.
  • New behavior: Unsubscribes the guest from marketing messages.
  • API documentation link: List all memberships of a guest

Membership

  • API Endpoint: {api_url}/v1/guests/{guestId}/Memberships

  • Scenario: This API has been enhanced to retrieve the list of memberships according to their status (Active/Inactive) using the new parameter ‘is_active’. When it receives the ‘is_active’ parameter as 0, it fetches all inactive memberships, and when it receives the parameter as 0, it fetches all active memberships.

  • Earlier behavior: This API fetched a list of all memberships without considering the status of the memberships (active/inactive).

  • New behavior: When it receives the ‘is_active’ parameter as 0, it fetches all inactive memberships, and when it receives the parameter as 0, it fetches all active memberships.

  • API documentation link: