# Production Documentation > Create a custom event experience and access all of your event data with the Accelevents API. ## Guides - [Accelevents API Documentation](https://developer.accelevents.com/docs/accelevents-api-documentation.md) - [Accelevents API Key](https://developer.accelevents.com/docs/getting-started.md) - [Adding Attendees](https://developer.accelevents.com/docs/adding-attendees.md) - [Attendees Analytics](https://developer.accelevents.com/docs/attendees-analytics.md) - [Exchange Ticket Type](https://developer.accelevents.com/docs/exchange-ticket-type-1.md): This is the technical documentation for the ticket exchange. We have given the option in host side order listing page to exchange the individual ticket. ## API Reference - [Get All Attendees](https://developer.accelevents.com/reference/get-all-attendees.md): This API will help to get all attendees of event. We need to pass authentication and event URL to get particular event's attendees. We are also using pagination and searching functionality for get records. - [Check whether "recurring event" is enabled](https://developer.accelevents.com/reference/check-recurring-event-is-enable.md): This API is used to check whether the event is recurring or not. This API will return a Boolean value like true or false. - [Get list of ticketing sales data](https://developer.accelevents.com/reference/get-list-of-ticketing-sales-data.md): This API will get ticketing sales data to display on the dashboard. By default ticket data type details will be fetched and can be changed to display ADDON type details. Path Parameters Not Required Body Parameters Not Required Response Details / Check response object Authentication required - ✅ Role wise accessibility 
 Super Admin - ✅ Admin - ✅ Staff - ❌ Attendee - ❌ Exhibitor - ❌ Speaker - ❌ Modules Display - ❌ Portal - ❌ Host - ✅ - [Get all sessions for display and portal page](https://developer.accelevents.com/reference/get-all-sessions-for-display-and-portal-page.md): Using this API, you can get sessions details for an event. You need to send `eventurl` as a path parameter. You can pass `page`, `size`, `expand`, `tagIds`, `trackIds`, `sessionFormat`, `past`, `showPastAndUpcoming`, `filterDate` and `calledFrom` as query parameter for pagination and filter support. This API can be used by any registered attendee within the event. - [Register/Bookmark session](https://developer.accelevents.com/reference/user-register-event-ticket-id.md): Use this API to add a bookmark to a session for an attendee. You need to send `true` for query parameter `joinSession` if the attendee register/bookmark session before it's live. If the attendee registers for a session after the session ended, then you need to send `pastJoinSession` as `true` within the query parameters. If for the session `allowedMinutesToJoinLate` is set `true`, and you try to register after the session ended then recording of this session is not available, it's only available for the attendees who have watched the session when it's live. This API can be used by authenticated users only, and it will require super admin/event admin/event staff/attendee level access. - [Unregister/remove a session from the bookmark](https://developer.accelevents.com/reference/user-unregister-event-ticket-id.md): This API is used to unregister a session or remove a session from the bookmark. To call this API you need to send `sessionId` and `userId` in the request body. This API can be used by authenticated users only, and it will require super admin/event admin/event staff/attendee level access. - [Get all attendee's registered sessions](https://developer.accelevents.com/reference/get-users-registered-sessions.md): Get all registered sessions for the specified event. This API can be used by authenticated users only, and it will require super admin/event admin/event staff/attendee level access. - [Create tag/tracks](https://developer.accelevents.com/reference/create-tag-and-tracks.md): Using tags and tracks you can label sessions and group them according to your convenience. It helps to filter out sessions based on tags and tracks. To create tags or tracks for an event same API endpoints are used. They are differentiated by `type` field. For tags and tracks `type` fields' values should be `TAGS` and `TRACKS` respectively. `type` and `name` are required fields, apart from them you can also pass additional fields like `color`, `position`, `description`. This API can be used by authenticated users only and it will require super admin/admin/staff level access. - [Get Sessions List](https://developer.accelevents.com/reference/get-all-sessions-1.md): This API will return a list of sessions for a particular event. `eventId` is the required query parameter. Apart from that, you can pass `searchString`, `page`, `size`, `isFromBillingPage`, and `expand` as query parameters. Only authorized users can use this API and require event admin, event staff, and super admin access. - [Update Session](https://developer.accelevents.com/reference/update-session.md): Using this API, you can update session details. You need to identify session id and send it as `id` path parameter. We recommend sending at least `title`, `startTime`, ticketTypesThatCanBeRegistered, format, and `endTime` fields in the request body to create a session. Apart from that, you can also send other attributes related to the session defined in body parameters. Using `sessionVisibilityType` you can set the session as private/public. If the session is set as private then it will be only visible to attendees who are pre-registered by the event admin. For all other attendees, the session will be hidden. You can not set sessions as private for the In-person event and also for the hybrid event type, you can not set the session as private for the In-person ticket. Only authorized users can use this API and need the event admin, event staff, and super admin. - [Get speakers list](https://developer.accelevents.com/reference/get-all-speakers.md): Using this API, you can get speakers list for a particular event. You have to send `eventId` as a query parameter. Apart from that, you can pass `searchString`, `page`, `size` & `expand` as query parameters for pagination & filter data. This API can be used by authenticated users only, and it will require super admin, event admin, event staff level access. - [Create speaker](https://developer.accelevents.com/reference/create-speaker.md): Using this API, you can create a new speaker for a particular event. You need to send `SpeakerDTO` as a request body, which contains information like `firstName`, `lastName`, `email` etc. If a speaker with the same email already exists you will get the error `4068906`. This API can be used by authenticated users only, and it will require super admin, event admin, and event staff level access. - [Update Ticketing Holder Attributes Data by Barcode Id](https://developer.accelevents.com/reference/update-ticketing-holder-attributes-data-by-barcode-id.md): This API updates ticket holder attribute data based on the barcode ID for a specified event and is accessible via API key or event admin token. The API returns a response containing a type and message. To call this API, the user must include query parameters in the URL, such as the event URL, barcode ID, attendee attribute details, and an authentication key. - [Exchange Ticket Type](https://developer.accelevents.com/reference/exchange-ticket-type.md): This API is used to exchange the event ticket of the user. - [Get all sessions for attendee](https://developer.accelevents.com/reference/get-all-sessions-for-attendee.md): This API is used to get all Sessions for attendee. - [Download Ticket Holder Data in CSV Format](https://developer.accelevents.com/reference/download-ticket-holder-data-in-csv-format.md): This API used to download the ticket holder data in CSV format for a specified event. - [Download Ticket Buyer Data in CSV Format](https://developer.accelevents.com/reference/download-buyer-holder-data-in-csv-format.md): This API used to download the Ticket Buyer data in CSV format for a specified event. - [Get People List/ Filtered People List](https://developer.accelevents.com/reference/get-people-list-filtered-people-list.md): This API is used to get the Attendees from the event. To apply a filter, need to pass the JSON object with the title, company, and interest and set the variable value accordingly (i.e. the set company which needs to filter.). The areas that are used for the filter are company, job title, and interests To get all people list, in JSON object title, company, interest, and interest ID's should be an empty array and search. The string should be an empty string. To apply the search feature, need to pass the value on searchString and it would be searching on the attendee's first name, last name, interest, job title, and company.