v2026.02.2

Summary#

v2026.02.2 updates composite event microphone responses and threshold update behavior. The documentation has also been revised to clarify timestamp precision and the conditions that trigger authentication errors.

Changed#

• Composite Events: In list, detail, and live responses, each mics[] item has been changed to return only the same nine fields as the Get A Mic Device response: id, name, host, edge_id, status, thresholds, location, created_at, and updated_at. Other fields are removed from mics[]; the nested events[].microphone object is unchanged. For examples, see the Composite Events API Overview.
• Timestamps: started_at may include fractional seconds with up to six digits of precision. When using this value, we recommend an ISO 8601 parser that accepts timestamps with or without fractional seconds.
• Mic updates: Update A Mic Device has been changed to update only the supplied threshold values. Each event type maps to an object containing sound_level_ge (0 to 100) and confidence_ge (0 to 1). Out-of-range values return 422. A 400 response has been added for unsupported event types, with message: 'This firmware SKU does not support the requested event classes'.
• Authorization: The API has been updated to return the existing expired-token 401 response when the session that issued an Access Token has ended, even before the token expires. A deactivated account returns the existing invalid-token 401 response. For details, see Authorization.