Johnny Lin: No specific updates to share at the moment, but we'll be discussing these as we plan upcoming product cycles.
I'd even like the API to provide this list - I need it so badly!
Bastien Vairet: The list of attendees are available via the `attendees` array on Event resources in the API: https://developers.savvycal.com/api/schemas/event
Derrick Reimer OK, but my use case is to create a record in a database for each participant in a group event. Is this possible? For example, if a group event has registered 6 participants, each time one of these participants registers for the event, a new line must be created in my database. The last time I tried this, it wasn't possible. However, if you need to track individual people who attend group events, this is necessary.
Bastien Vairet: We do send a `event.attendee.added` webhook anytime someone joins a group event: https://developers.savvycal.com/api/schemas/eventattendeeadd…, so this can be used to take programmatic action when someone joins an event.
Derrick Reimer Thank you, but is it possible to have the person's contact details each time? Last name First name Mail Phone and custom Field? Your support said the opposite some time ago
Derrick Reimer Sorry, in reality the problem wasn't quite that, but the fact that the event_id was unique for all the participants and that this prevented me from following the postponements or cancellations of a particular participant. That's a slightly different problem. Has this been resolved today?
Bastien Vairet: The event ID is not unique for each participant. We have webhooks for when an event attendee reschedules, where the original event and new event are included the payload (https://developers.savvycal.com/api/schemas/eventattendeeres…) and for when an attendee cancels from a group event (https://developers.savvycal.com/api/schemas/eventattendeecan…)
Derrick Reimer actually I'm sorry, I think I got confused. What I need for group bookings is a unique event ID while being able to differentiate participants by a participant ID. Because for some use cases, I need to count on the organizer side and for other use cases I need to count on the participant side. I looked into it, and it wasn't possible. Can you confirm this?
Bastien Vairet: Not sure I'm completely following, but yes the event ID (e.g. "event_XXX") stays constant for group events, and each person attending a group event gets a unique attendee ID (e.g. "attendee_YYY").
Derrick Reimer yes, but let's say one of the attendees cancels his participation or chooses another group slot. With which identifier can I update my database? the event_id isn't enough, since it doesn't identify the attendee, and the atendee_id isn't enough, since it doesn't identify the event. However, the cancel trigger doesn't allow me to retrieve the event_id and atendee_id.
Bastien Vairet: I see, in that case keying off the attendee's email address is probably the safest bet.
Derrick Reimer no email address is the worst possible solution. Users make typing errors, change their email address like they change their shirt. I sell my time online and I have to invoice my customers according to the time they spend with me: I can't afford any approximations of this kind, especially with such complex automation. Can I ask for an improvement on this point? If so, how? What title should I give to my feature request so that it's understood by your team?
Bastien Vairet: It sounds like you’re looking for more of a “scheduling portal” experience, where the person booking must authenticate so their identity stays consistent across bookings. Even that approach isn’t completely foolproof (for example, someone could sign up and book as bob@example.com and later return as bobjones@example.com), but it does provide a higher level of rigor. This is a bit beyond the scope of a general-purpose scheduling tool like SavvyCal today, but we’ll keep an eye out for similar requests.
Derrick Reimer I don't think I'm asking for a planning portal. Maybe I just need to add a little something to the API? I simply need to be able to delete or update a record in my database when a participant cancels his participation in a group event or postpones his participation in another group event. Do you confirm that this is currently impossible and that it couldn't be a possible improvement to the API?
Bastien Vairet: If you treat a participant’s email address as their identity, then these changes can be tracked—for example, when someone uses the reschedule flow to move from one group event slot to another, their email remains the same and the change can be attributed correctly. If an email address isn’t sufficient for your tracking needs, then you’d need some other form of verifiable participant identity, which SavvyCal doesn’t currently provide.
Derrick Reimer sorry but I don't understand why this can't be an API enhancement. I made a request here: https://feedback.savvycal.com/feature-requests/p/improved-we… If I'm wrong, I'm willing to try again to understand why.
Bastien Vairet: I followed up on that request. We'd be happy to continue the discussion over support email.
Derrick Reimer any plans for improvements on this front? And with group scheduling as a whole?