Error "Unable to use the video in an ad creative. Video id XXX,XXX,XXX,XXX,XXX might not be id of a video, or you might not have permission to see it"

Error "Unable to use the video in an ad creative. Video id XXX,XXX,XXX,XXX,XXX might not be id of a video, or you might not have permission to see it"

  1. Blog
  2. 15 November 2026
  3. 3 min read

Stefan Bogdanescu

Founder & Senior Architect

Decoding the "Invalid Video in Ad Creative" Error on Facebook

When integrating with the Facebook Ads API, distinguishing between a transient network hiccup and a fundamental permission or data mismatch is critical. The error you are encountering—Unable to use the video in an ad creative combined with error_subcode=2013004—is not a random failure mode. It specifically indicates that the entity referenced by the ID in your request does not exist as a valid, accessible video asset within the context of the user's account, or the token provided lacks the necessary scope to reference it.

The most common scenario leading to this specific issue is a scope mismatch between how the video was uploaded and how the ad creative is being created. You mentioned uploading the video using curl and receiving an ID immediately. However, Facebook distinguishes between two primary types of access tokens: User Access Tokens (issued via OAuth login) and Page Access Tokens (issued for business management).

If you used a User Access Token to upload the video, that video is attached to the user's personal profile or a specific page owned by that user. When you subsequently attempt to create an ad creative using a Page Access Token (which is standard for server-side automation), Facebook enforces strict privacy boundaries. If the Page token does not have explicit permission to see the video on the User account, the API rejects the video_id. The error message explicitly states, "might not be id of a video, or you might not have permission to see it."

Resolving the Permission Gap

To fix this, you must ensure that the token used in the access_token parameter of your ads_video_adcreative request has visibility into the specific video ID. There are two primary approaches:

  1. Use a Consistent Token Type: If the upload was done with a User token, the ad creation request must use that same User token (or a token with equivalent permissions). Mixing tokens often results in "Invalid parameter" errors because the system cannot resolve the cross-account reference.
  2. Explicit Permission Granting: If you prefer to keep using a Page Access Token for ad creation, you may need to grant the Page explicit permission to access the video. This is often done by accessing the user's profile settings and authorizing the business page to manage ads involving their personal content, though in many programmatic workflows, it is cleaner to ensure the upload and the creative creation happen within the same administrative context (e.g., both using a Business Manager Page token).

Handling Dynamic vs. Static IDs

You noted that hardcoding the ID works while passing it dynamically fails. This behavior suggests a potential variable scope issue or a mismatch in data types rather than the API logic itself. When you pass a dynamic $video_id, ensure that:

  • The variable is not inadvertently null or empty before reaching the json_encode step.
  • The string formatting matches exactly (e.g., no hidden whitespace).
  • The access_token passed in the request ($pass_token) is valid and has not expired.

In your code snippet, $object_story_spec relies on $video_id. If this variable comes from a previous API response, ensure you are parsing the JSON correctly to extract the integer or string ID without extra characters.

Implementation Example

Here is how to structure the request to ensure scope alignment and data integrity:

// Ensure $page_token has 'ads_read' and 'ads_management' permissions
// And ideally matches the context of where $video_id was created
$pass_token = "EAAB..._YOUR_PAGE_ACCESS_TOKEN_HERE"; 

$object_story_spec = [
    'page_id' => $page_id, 
    'video_data' => [
        'video_id' => $video_id, // Must be visible to $pass_token
        'message' => $ad_message,
        'image_url' => $image_url,
        'title' => $ad_header,
        'call_to_action' => [
            'type' => 'LEARN_MORE', 
            'value' => ['link' => $ad_redirect]
        ]
    ]
];

$params = [
    'url_tags' => 'utm_source=facebook',
    'image_url' => $image_url,
    'object_story_spec' => json_encode($object_story_spec),
    'access_token' => $pass_token,
];

$response = $fb->post('ads/video_adcreatives', $params);

If the upload was performed via a curl command using a different token than the one stored in your application, the solution is to re-upload the video using the same Page Access Token intended for ad creation. This ensures the asset is owned by the Business Manager entity that will be billing and serving the ads, eliminating cross-account permission errors entirely.

Our network