Changelog
Every published change to the v1 surface, from the same source the API serves.
Versioning and compatibility
Within v1, changes are strictly additive: a published field never changes name, type or meaning. A breaking change ships as a new version, and the previous one stays supported for at least 12 months from its changelog announcement.
ADDITIVE means you can update without touching your integration: within v1 only fields and capabilities are added — nothing is renamed or removed. If something ever had to break, it would ship as a new version, announced in this history at least 12 months ahead.
- ADDITIVE
The participant roster now says how each person was let in: identity_seal is VERIFIED when an identity provider vouched for them, GUEST when they came through the invited-guest link, and UNVERIFIED when neither happened. Without it an integrator reading a roster of names could not tell which of them anyone had actually checked. Additive: no existing field changed. The same release finishes naming two closed domains the document was already enforcing but never said out loud: the export format (csv, xlsx) and the webhook connector (ZAPIER, POWER_AUTOMATE) — until now the only way to learn either was to send a wrong value and read the 400.
- ADDITIVE
Per-question results now carry the spinner wheel's spin log (spin_outcomes) and, for ordering questions, how many people put each item in each position (placement_accuracy[].counts_by_position). Both were produced internally and never published; a spinner wheel's results envelope used to arrive empty. Additive: no existing field changed.
- ADDITIVE
Discovery without a credential: the enforced rate limits, the webhook retry schedule and the published event catalogue, plus this changelog itself.
- ADDITIVE
Self-serve webhooks: register, remove and re-enable endpoints, list them, read their delivery history including dead-lettered attempts, and redeliver one manually.
- ADDITIVE
Content management with a content:write credential: create sessions from a presentation, open, close and schedule them, author and update questions, and put a question on the room's screen.
- ADDITIVE
Public API v1: read an organization's presentations, sessions, KPIs, per-question results, Q&A, exports and participants with a results:read credential.