LinkedIn: reuse one uploaded video in a feed post and a sponsored ad
LinkedIn says a video uploaded through the Videos API can be reused across post formats. Upload your Sume avatar clip once, then reference its URN twice.
Yes. LinkedIn's Videos API page says a video uploaded for the feed can also be used in a sponsored video ad without a separate upload. Upload your finished avatar clip once, keep the urn:li:video:... it returns, and reference that URN in both the organic post and the ad creative.
What does the Videos API say about reuse?
A note on the page: videos uploaded with the Video Ads API can now be reused across different video post formats, for example a video uploaded and posted to the feed can be used in a sponsored video ad. The API replaces the older Assets API and returns a specific video URN. Uploads can optionally carry mediaLibraryMetadata, which also registers the asset in an ad account's media library, and the media library status defaults to ACTIVE.
| Item | What the page says |
|---|---|
| Reuse | One uploaded video can serve feed and sponsored formats |
| Owner | A person or organization URN in initializeUploadRequest |
| Permissions | Company owners need ADMIN or DSC page permission; members must match the owner |
| Media library | Optional mediaLibraryMetadata registers the asset in an account library |
| Scopes | w_organization_social, w_member_social, rw_ads |
Why does it help with avatar clips?
An avatar render costs money and queue time. The Avatar 1.0 docs bill by quality tier (standard, plus, max) and the video is 720p. Rendering once and reusing the upload means the organic post and the ad show identical frames, and your reporting compares the same creative.
Keep one Sume job id per creative. The jobs docs say to store the id so you can recover work after a restart.
What can go wrong?
Permissions come first. A 403 says accessing the video resource is forbidden, and the page ties it to owner rules: company URN owners need ADMIN or DSC permissions, and member owners must match the caller. For ads you also need rw_ads on the sponsored account.
Aspect ratio is the second trap. Avatar 1.0 supports 1:1, 3:4, 9:16, 4:3 and 16:9. The Videos API page points to LinkedIn's Video Ads specifications for ratio rules, and I did not fetch that page, so confirm your ratio there before choosing between 1:1, 9:16 and 16:9.
curl -X POST https://api.sume.com/v1/avatar-1.0/talking-video \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: li-one-upload-001" \
-d '{
"avatar_handle": "product_host",
"aspect_ratio": "1:1",
"script": "Our new release saves your team an hour a week."
}'Limits of this approach
Reuse saves uploads, not approval. Ad review is LinkedIn's. Sume also does not publish to LinkedIn in the docs I read, so the upload and post calls are yours.
Sources
Related posts
More in Integrations
- LinkedIn video status PROCESSING_FAILED: read the reason, fix the clip
LinkedIn Videos API returns PROCESSING_FAILED with a processingFailureReason. Probe your Sume clip first and re-upload a clean file instead of guessing.
- Lovable custom MCP connector for Sume: API key, chat only
Add Sume's hosted MCP server to Lovable as a custom connector with a bearer API key. It informs project chat only and does not power published apps.
- Make removed Cycles per run on Oct 1: pace Sume submits instead
Make removed its Cycles per run setting on October 1, 2026. How to keep a Sume batch inside queue and rate limits without it, and when to use a bulk queue.
- Cline MCP remote not connecting: set type streamableHttp for Sume
Cline treats a remote server with no type as legacy SSE. Sume's hosted MCP is streamable HTTP and answers GET /mcp with 405, so set type to streamableHttp.
Written by Sume