Staying in sync

Your records can always match the meeting, even if your server was down when an update arrived.

Spot a gap

Sequence numbers for a meeting run 1, 2, 3 with nothing skipped. If you hold 4 and receive 6, update 5 is missing. Check for gaps before you treat a meeting as over.

Fill it

GET /meetings/{externalId}/events?afterSequence=4&limit=100

The history returns the same updates, with the same ids and numbers, as the deliveries did, so nothing is recorded twice. Keep reading while hasMore is true, using nextAfterSequence. The page also tells you how many days of history are kept (retentionDays).

Check the whole meeting

GET /meetings/{externalId} gives the meeting as it is right now, guest by guest. It and the updates come from the same source, so they never disagree.