Jifflenow: Enhanced API Sync - Track & Manage Removed Participants Seamlessly

Currently, when a participant is removed from a meeting in Jifflenow, they are entirely excluded from the API response. This creates data inconsistencies in external systems, leaving stale participant records. As a result, meeting organizers and integrated platforms may act on outdated information, impacting operational efficiency and reporting accuracy.

Solution

1. New Attribute for Removed Participants

   • Introduce a user_removed_status attribute (Boolean) in the API response.

   • When a participant is removed, they will not be deleted but instead marked as user_removed_status: true.

   • The invite_status field will continue to track RSVP status separately.

2. Seamless Delta Sync for Updates

   • The removal status will be included in delta sync updates to external systems.

   • Third-party integrations will automatically receive updates without requiring a full data refresh.

3. Query Parameter for Customization

   • Add a new query parameter api_params[include_removed_users] to meeting/session API endpoints.

   • Customers can choose to include removed participants in the API response by specifying this parameter.

4. Backward Compatibility & Default Behavior

   • The API will not include removed participants by default unless the query parameter is explicitly enabled.

Sample API

GET /api/adapter/Event2025/meetings_list?api_params[include_removed_users]=true

Initial Sync Response
(All participants are included with user_removed_status: false by default.)
[
{
"meeting_id": 101,
"participant": "Alice",
"invite_status": "Approved",
"user_removed_status": false
},
{
"meeting_id": 101,
"participant": "Bob",
"invite_status": "Declined",
"user_removed_status": false
},
]

If Bob is Removed from the Meeting, instead of deleting Bob, user_removed_status will be updated to true.

Delta Sync Response (Only returning updated records to reflect changes.)

[
{
"meeting_id": 101,
"participant": "Bob",
"invite_status": "Declined",
"user_removed_status": true
"last_sync_at": "2025-02-03T12:00:00Z"
}
]