# 2.29.0

By Steven Van · 2026-10-08

Direct API uploads can now preserve historical meeting dates and save the attendees supplied with the recording.

Historical recordings imported through [Fireflies.ai](<https://creatorstoolbox.com/tools/fireflies>)’s createUploadUrl mutation can now use the actual meeting start time instead of the upload time. The [2.29.0 update](<https://docs.fireflies.ai/getting-started/whats-new#2-29-0>) adds an optional meeting\_date field to CreateUploadUrlInput, matching the field already supported by uploadAudio.

## Set the meeting date

The field accepts an ISO 8601 string: YYYY-MM-DD alone uses UTC midnight, while YYYY-MM-DDTHH:MM:SS\[.fff\] accepts Z or a ±HH:MM offset. The date must be strictly after 1970-01-01T00:00:00Z and cannot be in the future. Omitting it keeps the existing behavior of using the upload time.

## Save attendees with the meeting

Attendees passed to createUploadUrl are now saved on the meeting. An attendee is dropped if their email contains the uploader’s email as a substring, using a case-sensitive comparison.

![Fireflies.ai](<https://www.google.com/s2/favicons?domain=fireflies.ai&sz=128>)

Fireflies.ai

Automatically take notes, transcribe, summarize, search, and analyze all your team conversations in one place. It works across any video conferencing platform.

[View Fireflies.ai →](<https://creatorstoolbox.com/tools/fireflies>)

[Original source](<https://docs.fireflies.ai/getting-started/whats-new#2-29-0>)

[Read 2.29.0 on Creators Toolbox](<https://creatorstoolbox.com/blog/fireflies-ai-2-29-0>)

---
Canonical source: https://creatorstoolbox.com/blog/fireflies-ai-2-29-0