Store a Vortex Desktop recording from a URL, without transcribing it
Downloads the recording from the presigned URL, stores it where Pro's own audio uploads go and creates the Audio record. It is never transcribed: Vortex Desktop has already detected the brands and assets, so no transcription or matching job is started and the transcription fields stay empty. Attach the returned id to the report with POST /api/vortex/user-event-uploads (media_type audio) so the review screen lists and plays it, and to rows with items..audios..id on POST /api/vortex/audit/audio-bulk. The URL must be a direct presigned GET whose path ends with m4a, mp4, mp3 or wav; the file must be at most 500 MB and arrive within 120 seconds, so callers should allow at least 300 seconds for the whole request. Each call stores a new recording. Authenticated via X-API-Key.
Request
- Base URLhttps://api.sponsorunited.com (the document declares no server; this is the origin it was published from)
- AuthAPI key in header X-API-Key
- TypeScripthttps://skmtc.dev/sponsorunited/apis/sponsorunited-api/docs/api/vortex/upload-audio-from-url/post.tsA function with typed inputs. Its response is checked against the schema.
Request body
Example request
{
"url": "https://bucket.s3.amazonaws.com/sessions/abc/recording.m4a?X-Amz-Signature=...",
"user_id": 42,
"item_subplatform_id": 7,
"original_name": "Yankees vs Red Sox - WFAN.m4a",
"language": "en-US"
}Response
Recording stored
Example response
{
"id": 9876,
"stored_name": "9876_42_en-US_7_1760870400.m4a"
}Changes
No recorded changes to this operation across all 2 revisions of this API.