igpapi — Instagram private API Simulator for Node.js (API reference) 4.14.0
    Preparing search index...

    Interface ProfilePostsFeedVideoState

    What playing a video needs beside the address: the facts the view telemetry reports.

    interface ProfilePostsFeedVideoState {
        authorId?: string;
        carousel?: { children: readonly string[]; size?: number; slide?: number };
        dashManifest?: string;
        followsAuthor?: boolean;
        mediaId: string;
        position: number;
        startingClipsMediaId: string;
        takenAt?: number;
        trackingToken?: string;
        videoDuration?: number;
    }

    Hierarchy (View Summary)

    Index

    Properties

    authorId?: string
    carousel?: { children: readonly string[]; size?: number; slide?: number }

    The carousel's children from the grid answer; absent on a media that is no carousel.

    dashManifest?: string
    followsAuthor?: boolean
    mediaId: string
    position: number
    startingClipsMediaId: string

    The starting_clips_media_id the item's like carries: the pk of the clip the contextual feed was entered from, the feed's own fact (host.facts.firstMediaId). The app carries the field on the button like of the entered item itself, where the entry clip and the liked item are one media, so choosing the entry clip for a later item rests on the field's name, not on the app's behavior; the double-tap like carries no such field and is not modelled.

    takenAt?: number
    trackingToken?: string

    The grid answer's organic_tracking_token on the media: the repost note's tracking_token.

    videoDuration?: number