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

    Variable SearchResultsAccountsTabScreenConst

    SearchResultsAccountsTabScreen: ScreenDefinition<
        "SearchResultsAccountsTab",
        "innerTab",
        {
            query: string;
            session: {
                clientUuidRankToken?: string;
                searchSessionId: string;
                serpSessionId: string;
                typeaheadSessionId?: string;
            };
        },
        {
            users: readonly {
                fullName?: string;
                isPrivate?: boolean;
                isVerified?: boolean;
                rowKey: string;
                userId?: string;
                username?: string;
            }[];
        },
        Record<never, never>,
        IgApiError | HttpRequestError,
        PlainJsonApiHttp | MobileDevice | NavigationWire | MobileNavigation,
        SearchResultsAccountsTabActions,
        SearchResultsAccountsTabItems,
        never,
        never,
    > = ...

    The Accounts tab of the search results (serp_users): the top-tab switch inside the results screen in front (serp_top becomes serp_users in place, same ordinal and source). The enter requests the account results (AccountSerp, whose lat/lng are the device's known position) and then switches the tab; the accounts are items.

    Not modelled: the next page. The answer carries its continuation, but the app's request for a second page of account results is not known, so the screen has no nextPage action and keeps no cursor.

    Confirmed on Android 451: the accounts tab in front, its results opened back into a profile.

    Screenshot: screenshots/results-accounts-tab.webp beside search.results.ts.

    Guide: Search