Skip to main content

​
Overview

QA Wolf accepts file uploads via a two-step signed URL process:
  1. Request a signed upload URL from the QA Wolf API
  2. Upload your file directly to that URL
This method works for any supported file type and can be used for one-off uploads or as part of a custom automation.
Only the following file types are accepted: .apk, .aab, .deb, .ipa, .zip, .csv, .pdf

​
Prerequisites

  • Your QAWOLF_API_KEY — available under Workspace Settings → Integrations → API Access

​
Step 1: Generate a signed URL

Make a GET request with the filename (including extension) as the file query parameter. 
curl -X GET \
  "https://app.qawolf.com/api/v0/run-inputs-executables-signed-urls?file=YOUR_FILENAME" \
  -H "Authorization: Bearer $QAWOLF_API_KEY"
On success, you’ll receive: 
{
  "fileLocation": "$TEAM_ID/YOUR_FILENAME",
  "playgroundFileLocation": "YOUR_FILENAME",
  "signedUrl": "https://..."
}
Copy the signedUrl — you’ll use it in the next step.
The signed URL is temporary. Upload your file promptly after generating it.

​
Step 2: Upload the file

Use the signedUrl from Step 1 to upload your file via a PUT request. 
curl -X PUT \
  --header "Content-Type: application/octet-stream" \
  --data-binary @./path/to/your/file \
  "$SIGNED_URL"
Once this completes successfully, the file is available in QA Wolf.

​
File-specific notes

Use a static filename based on the environment (e.g., app-staging.ipa) so tests always reference the latest build. See Integrating your mobile CI pipeline for how to automate this as part of your build process.
ZIP files can be used to bundle multiple assets for a single upload. Ensure the contents follow any structure expected by the tests that will consume them.
CSV files are typically used as test data inputs. Use a consistent filename so flows always pick up the latest version.
PDF files can be uploaded for use in test flows that involve document handling or validation.
Last modified on March 25, 2026