Skip to main content
Direct upload is available on every paid plan (Pro or higher). An admin can disable file uploads for your organization, and the mutation then returns feature_disabled.

Overview

The createUploadUrl mutation generates a pre-signed URL that allows you to upload audio or video files directly to Fireflies.ai storage. This is useful when you want to upload files from your own infrastructure without exposing them via a public URL. Choose how you will upload the file with upload_method:
  • POST (recommended): a pre-signed form, a URL and the form fields signed for it. It only accepts a file within the size limit for its type; storage refuses a larger file.
  • PUT (the default when upload_method is omitted): a pre-signed URL that takes the file as the request body. Storage accepts a file of any size; confirmUpload then refuses one over the size limit.
This mutation is part of a two-step upload flow:
  1. Call createUploadUrl to get a pre-signed upload URL (and, for POST, its form fields)
  2. Upload your file to upload_url with the returned upload_method. See Uploading the File
  3. Call confirmUpload to confirm the upload and start transcription

Arguments

CreateUploadUrlInput
required

Response

String
The URL to upload your file to, with upload_method. See Uploading the File.
UploadMethod
The HTTP method of the upload: the upload_method you requested, or PUT when you did not request one. For POST, send a multipart form with every upload_fields entry, then the file last, as the field named file. For PUT, send the file as the request body, with a Content-Type header equal to the content_type you requested.
[UploadFormField!]!
For POST, the form fields the upload was signed with, as name and value pairs. Send each one unchanged as a form field, in any order, before the file. The names depend on the storage provider (for example key, Content-Type, policy and x-goog-* fields, or Policy and X-Amz-* fields), so read them from the response instead of hard-coding them. See UploadFormField. Empty for PUT.
String
The unique identifier for the meeting. Use this ID when calling confirmUpload.
String
ISO 8601 timestamp indicating when the upload URL expires. URLs are valid for 1 hour.

Usage Example

Uploading the File

Upload the file to upload_url with the upload_method of the response. You can upload again with the same upload_url (and, for POST, the same fields) until expires_at; a new upload replaces the previous file.

POST (recommended)

With upload_method: POST, upload the file to upload_url with an HTTP multipart form POST (multipart/form-data):
  1. Send every entry of upload_fields as a form field, with its name and value unchanged. Their order does not matter.
  2. Send the file last, as the field named file. The storage ignores any field after the file.
Do not add a Content-Type header of your own to the request; your HTTP client sets it with the form boundary. The storage answers a successful upload with a 2xx status, usually 204 No Content. It refuses a file larger than the size limit for its type, an upload after expires_at, and a form whose fields were changed, with a 4xx error. With curl and jq in bash, where response.json holds the createUploadUrl response:
--form-string sends each value as plain text: with -F, curl would read a value starting with @ or < as a file name.

PUT

Without upload_method, or with upload_method: PUT, upload_fields is empty. Upload the file to upload_url with an HTTP PUT request: the file as the request body, with a Content-Type header equal to the content_type you requested. Storage does not limit the size of a PUT upload; confirmUpload refuses a file over the size limit for its type.
After the upload completes successfully, call confirmUpload to start transcription.

Supported Content Types

Audio Formats

Video Formats

File Size Limits

Daily Limit

Each upload URL creates a meeting, so each user can create at most 50 upload URLs per day (UTC), whether or not the files are later confirmed. Upload URLs created before the limit was reached can still be used and confirmed.

Error Codes

The content type is not supported, or the file size exceeds the allowed limit for your plan.
Your organization admin has disabled file uploads for transcription. Contact your admin to re-enable uploads. See feature_disabled.
You have created 50 upload URLs today (UTC). extensions.metadata.retryAfter is the next UTC midnight, in milliseconds since the epoch. See too_many_requests.

Audit Trail

A successful call records a MEETING_UPLOAD_CREATED audit event carrying the contentType and fileSize in its metadata.

Additional Resources

Confirm Upload

Confirm the upload and start transcription

Upload Audio (URL)

Alternative: Upload audio via public URL

Webhooks

Receive notifications when transcription completes

Language Codes

Supported language codes for transcription