> Portal Navigation: > > - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version. > - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages). > - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`). > - Top-level index of all portals: https://dev.wix.com/docs/llms.txt > - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt ## Resource: Introduction ## Article: Introduction ## Article Link: https://dev.wix.com/docs/api-reference/business-management/calendar/participations-v3/introduction.md ## Article Content: # About the Participations API The Participations API lets you manage participation details for [events](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/introduction.md) and [schedules](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction.md). With the Participations API, you can: + Create and update `participation` objects. + Retrieve `participation` objects. + Delete `participation` objects. For more in-depth event management, see: + [Events API](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/introduction.md) + [Schedules API](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction.md) + [Bookings APIs](https://dev.wix.com/docs/rest/business-solutions/bookings/about-wix-bookings.md) ## Before you begin It’s important to note the following points before starting to code: + Whenever you create, update, or delete a `participation` object, the corresponding events' `participants` and `remainingCapacity` fields are automatically updated. + Depending on your implementation, either the business owner or the participant may have to confirm participation. For example, in Wix Bookings the business owner needs to confirm bookings. + Wix Bookings automatically manages participation details. Therefore, you shouldn't create, update, or delete participations when extending Wix Bookings. Doing so may lead to data inconsistencies and unexpected behavior in your implementation. ## Use cases + [Create a participant dashboard](https://dev.wix.com/docs/rest/business-management/calendar/sample-flows.md#create-a-participation-dashboard). ## Terminology + **Participation**: Representation of the relationship between a participant and an [event](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/event-object.md) or [schedule](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/schedule-object.md). It includes details about the participant, whether the participation status is confirmed or pending, which app owns the relevant event or schedule, and allows for custom data extensions. + **Status**: Status of the party's participation in the event. Depending on your implementation, either the business owner or the participant may have to confirm participation. For example, in Wix Bookings the business owner must confirm bookings. @sdk_package_setup