Skip to main content
This API is not generally available. Whitelisting is currently closed.

Overview

The confirmUpload mutation confirms that a file has been successfully uploaded to the pre-signed URL and triggers the transcription process. This is the second step in the direct upload flow. Upload Flow:
  1. Call createUploadUrl to get a pre-signed upload URL
  2. Upload your file directly to the URL using an HTTP PUT request
  3. Call confirmUpload to confirm the upload and start transcription

Arguments

ConfirmUploadInput
required

Response

Boolean
Indicates whether the confirmation was successful and transcription has been queued.
String
The meeting ID for the confirmed upload.
String
A message describing the result of the confirmation.
String
Link to the meeting in Fireflies. It opens right away; the transcript appears there once processing finishes (usually a few minutes).

Usage Example

Complete Upload Flow Example

Here’s a complete example showing the entire upload flow:

Error Codes

The upload session was not found or has expired. Upload sessions expire after 1 hour. You need to call createUploadUrl again to get a new upload URL.
The file was not found in storage. Make sure you have successfully uploaded the file to the signed URL before calling this mutation.
Your organization admin has disabled file uploads for transcription. Contact your admin to re-enable uploads. See feature_disabled.
This upload was already confirmed, by an earlier call or one running right now. The file is transcribed once; open the meeting link in the message instead of uploading the file again.
Fireflies could not tell whether processing started (for example, the request timed out). The message says so and links the meeting: check it before uploading again, since it may still be transcribed. The same upload cannot be confirmed again for up to an hour; if the meeting gets no transcript, upload the file again with a new createUploadUrl.

Important Notes

  • Upload sessions expire after 1 hour. If you don’t confirm within this time, you’ll need to start over with a new createUploadUrl call.
  • Make sure the file upload to the signed URL completes successfully before calling confirmUpload.
  • The meeting_id must match the one returned from createUploadUrl.
  • Only the user who created the upload session can confirm it.
  • Confirm each upload once. Until the upload session expires (1 hour after createUploadUrl), a second call is refused with invalid_arguments and the meeting link, so the file is never transcribed twice.

Audit Trail

A successful call records a MEETING_UPLOAD_CONFIRMED audit event for the meeting.

Additional Resources

Create Upload URL

Generate a pre-signed URL for uploads

Webhooks

Receive notifications when transcription completes

Transcript

Query the transcript after processing

Upload Audio (URL)

Alternative: Upload audio via public URL