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

    Interface DiscoverChainingInput

    interface DiscoverChainingInput {
        profileRow?:
            | { entryPoint: "profile_auto_expand"; targetUsername: string }
            | { entryPoint: "profile_post_follow" }
            | { entryPoint: "profile_chaining_button" };
        targetId: string;
    }
    Index

    Properties

    profileRow?:
        | { entryPoint: "profile_auto_expand"; targetUsername: string }
        | { entryPoint: "profile_post_follow" }
        | { entryPoint: "profile_chaining_button" }

    The profile screen's suggested-users row (Android 451): sent together as consumption_surface=profile_hscroll and module=profile when given. The row has three forms, and only the opening one carries the profile's username and the module it was reached from. That module is the screen in front's endpoint module, read from the navigation state — never a caller argument, so the body and the headers cannot name different screens.

    Type Declaration

    • { entryPoint: "profile_auto_expand"; targetUsername: string }
      • ReadonlyentryPoint: "profile_auto_expand"
      • ReadonlytargetUsername: string

        target_username, sent when the profile opens.

    • { entryPoint: "profile_post_follow" }
    • { entryPoint: "profile_chaining_button" }
      • ReadonlyentryPoint: "profile_chaining_button"

        The profile header's add-person ("suggested users") icon: the profile_chaining_button rail, with no target_username/from_module and both chaining flags off (android-451/follow-from-search, request_entry_point=profile_chaining_button).

    targetId: string

    User id/pk the suggestions are based on.