01Who this is for
- Product teams building messaging intensive SaaS platforms benefit because the flow prevents out of memory crashes during file uploads.
- Marketing teams that send large media via WhatsApp gain faster delivery and fewer upload errors.
- Support departments handling customer screenshots and videos avoid server load spikes with direct client uploads.
02Signed URL file uploads, explained
Signed URL File Upload is an infrastructure change within the Conversations API. Instead of routing file bytes through HighLevel servers, the platform returns a time limited, signed URL that points to a Google Cloud Storage object. The client then streams the file straight to GCS.
The upload proceeds in three distinct phases: Initiate, where metadata is posted and a signed URL is generated; Upload, where the client performs a PUT request directly to the signed URL; and Complete, where HighLevel confirms the stored object and returns a public link for use in messages. The signed URL expires after 15 minutes, and the system validates size, MIME type, and access rights at each step.
03How businesses use signed URL file upload
- Marketing agency. The agency creates a media post for a client’s WhatsApp campaign. It first calls the Initiate endpoint with file metadata, receives a signed URL, uploads the video directly to GCS, then calls Complete to obtain the URL that will be inserted into the WhatsApp message.
- Ecommerce retailer. When a customer requests a product demo video via SMS, the retailer initiates the upload flow, streams the video file straight to GCS, and completes the process to embed the public link in the outgoing SMS, keeping the server free of large file buffers.
- Healthcare clinic. The clinic’s portal allows patients to attach medical documents to a chat. The portal initiates a signed URL request, uploads the PDF directly to GCS, and completes the upload to receive a secure link that can be shared within the encrypted conversation.
04The numbers and rules that matter
- WhatsApp uploads up to 100 MB.
- Other channels up to 5 MB.
- Signed URLs expire after 15 minutes.
05How to set up and use signed URL file upload in HighLevel
Execute the three step Signed URL upload flow
- Call POST /conversations/messages/upload/initiate with file name, size, and content type to receive a signed URL and object path.
- Send a PUT request from the client to the signed URL, streaming the file bytes and setting the Content Type header to match the file.
- Call POST /conversations/messages/upload/complete with the object path so HighLevel verifies the stored file and returns the public URL for messaging.
06Settings that matter
- Signed URL lifetime. Controls how long the generated upload URL remains valid; it expires after 15 minutes to limit misuse.
- Channel size limits. Defines maximum allowed media size per messaging channel: up to 100 MB for WhatsApp and up to 5 MB for all other channels.
- Content, Type validation. Ensures the declared MIME type matches the file extension on Initiate and that the stored object's MIME type matches the filename on Complete.
07Things to know before you rely on it
- WhatsApp supports media files up to 100 MB; all other channels are limited to 5 MB.
- Signed URLs expire after 15 minutes and cannot be reused for additional files.
- Files larger than the channel limit are rejected during the Initiate step.
- Mismatched MIME types cause validation failures at both Initiate and Complete stages.
08If something goes wrong
- Signed URL expires before upload finishes. Repeat the Initiate call to obtain a fresh signed URL, then resume the upload and complete steps.
- File size exceeds channel limit. Reduce the file size or choose a channel that allows a larger limit, such as WhatsApp for up to 100 MB.
- Content type mismatch error. Ensure the file extension and the Content Type header accurately describe the file before calling Initiate.
- Permission or path validation failure. Verify that the conversation exists, belongs to the specified location, and that the user has access to that location.
09How it connects to the rest of HighLevel
- Explore all conversation features and how file attachments work. All Conversations features
- Review pricing to see which plans include the Signed URL upload capability. HighLevel pricing and plans
- Start a trial to test Signed URL uploads in your own account. Start a 30 day HighLevel trial
Michael's take

Get the Initiate request as close as possible to the actual upload. That way the 15 minute window is fully available and you avoid unnecessary retries.
Test the Content Type header handling early, because mismatches will stop the flow before any data moves.