FirefliesAI Release Notes

Webhooks V2 can resend meeting.transcribed and meeting.summarized when a meeting that was already delivered gets a new transcript or summary, for example after reprocessing, a language change, regenerating notes or applying a refined summary.

Turn on Resend when a meeting's notes change on the webhook setup page; it is off by default.

Resent payloads include a new reprocessed_at field (Unix milliseconds of the change), which stays the same across retries and increases with each later change, so you can replace your stored copy when it is newer.

First deliveries are unchanged.

See Resends After a Meeting Changes.

The createBite mutation now accepts transcript_id, the name its documentation has always used. Until now the schema only accepted transcript_Id (capital I), so a request written from the docs failed with Unknown argument "transcript_id". transcript_Id keeps working and is deprecated; sending both with different values is rejected.

Documentation corrections: createBite's privacies is [BitePrivacy!]; the transcripts scope argument is a String (one of title, sentences, all) and the example declares organizers and participants as [String!], the type the schema expects; and AskFredMessage has no error field.

Raised the API rate limits and made them observable. Free moves from 50 to 500 requests per day with a 30 requests per minute burst limit; Pro moves from 500 to 5,000 requests per day with 60 requests per minute. Daily quotas still reset at midnight UTC. Business and Enterprise keep 60 requests per minute with no daily cap, now pooled across the team at 60 requests per minute per paid seat (up to 1,200 per minute on Business, 2,400 on Enterprise), so one integration can use most of the team's budget while no single user can take more than half of it (rounded up, and never less than their own 60 per minute); the Add to Live limit pools the same way (3 per paid seat per 20 minutes, up to 60). A paid seat is a seat on your subscription (or a billed member, if you have more of those); free seats such as campaign invites and internal accounts do not add to the team's budget. New Free API users get Pro limits for their first 14 days. Every response checked by the general API limiter now carries standard X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers (an allowed addToLiveMeeting response, metered by its own window, carries the suffixed X-RateLimit-*-call_join headers instead), and a 429 carries Retry-After in seconds; the MCP server's -32429 error carries the same header. The MCP server shares all of these limits. See Limits for details.

Set the real meeting date on direct uploads

The createUploadUrl mutation now accepts an optional meeting_date (ISO 8601 String) on CreateUploadUrlInput, the same field uploadAudio accepts. Use it when importing historical recordings so the meeting is dated with the actual meeting start time instead of the upload time. It accepts YYYY-MM-DD alone (UTC midnight) or YYYY-MM-DDTHH:MM:SS[.fff] with Z or a ±HH:MM offset, must be strictly after 1970-01-01T00:00:00Z, and must not be in the future; when omitted, the upload time is used as before. The attendees passed to createUploadUrl are now also saved on the meeting — note an attendee is dropped when its email contains the uploader's email as a substring (case-sensitive).