You have an image library (GET /v1/ads/images) that turns an image_hash into a direct, ungated CDN URL. There's no equivalent for video.
Asking for:
GET /v1/ads/videos — list an ad account's already-uploaded videos, each with a direct file URL → Meta: /act_{id}/advideos
and/or a per-video read returning source → Meta: GET /{video-id}?fields=source
accept an existing account video_id when creating creatives — today POST /v1/ads/creatives takes imageUrl/imageHash only, so video must be re-uploaded and can't be reused
Why it matters:
Per-asset reporting. asset_feed_spec.videos[] returns video_id + thumbnail_url only — Meta's asset schema has no video URL field — so in a DCO/flex ad we can show each video's thumbnail with its own spend, CPM and CTR, but never play the asset it belongs to.
Download + transcribe. We transcribe ad video to analyse hooks and scripts. That needs a direct file URL our app can fetch, exactly like your image URLs — not a login-gated watch page, which no automated download can pass.
Ad creation. Selecting a video already sitting in the ad account, rather than re-uploading a file we have no way to read back.
Note: ?fields=source already works for dark-post ad videos (per support), so even a thin proxy of that single call would unblock 1 and 2.
Please authenticate to join the conversation.
Completed
Feature Request
About 1 month ago

Joel Woolhead
Get notified by email when there are changes.
Completed
Feature Request
About 1 month ago

Joel Woolhead
Get notified by email when there are changes.