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

    Variable UserProfileReelsTabClipItemConst

    UserProfileReelsTabClipItem: ScreenItemDefinition<
        "UserProfileReelsTabClip",
        {
            code: string;
            id: string;
            media_type: number;
            organic_tracking_token?: string;
            pk: string;
            taken_at?: number;
            user?: { id?: string; pk?: string };
            video_duration?: number;
        },
        {
            code: string;
            id: string;
            media_type: number;
            organic_tracking_token?: string;
            pk: string;
            taken_at?: number;
            user?: { id?: string; pk?: string };
            video_duration?: number;
        },
        UserProfileReelsTabClipState,
        never,
        never,
        UserProfileReelsTabClipItemActions,
        {
            clips: readonly {
                code: string;
                id: string;
                media_type: number;
                organic_tracking_token?: string;
                pk: string;
                taken_at?: number;
                user?: { id?: string; pk?: string };
                video_duration?: number;
            }[];
        },
        never,
        never,
    > = ...

    One clip of the profile's Reels tab. Its open() pushes the reels viewer on the tab's whole list, at this clip's index (source clips_profile): the viewer's first page is that list and sends no stream.

    The viewer derives each reel's chaining facts from the list: the session's seed is the tapped clip's container id (while the like takes its pk part), the chaining position its distance from the tap and the client position its index in the tab's list. A clip the tab does not show has no index — the edge names -1 rather than falling back to the first clip, and the viewer refuses it as a typed ScreenDataError (ReelsViewer's list check).

    Settings

    Member Visibility