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

    Interface PigeonContext

    What one upload says about the identity whose events it carries and about the device and the process around it. Every field is a fact of that state: the identity's tokens and viewer, its checksums, whether the server has named it in this process.

    interface PigeonContext {
        appId: string;
        appVersion: string;
        appVersionCode: string;
        authTokens: string[];
        configChecksum: PigeonChecksum;
        deviceId: string;
        familyId: string;
        hmacTtlToken?: string;
        identityRequest: boolean;
        pigeonSessionId: string;
        samplingChecksum: PigeonChecksum;
        userId?: string;
    }
    Index

    Properties

    appId: string
    appVersion: string
    appVersionCode: string
    authTokens: string[]

    The identity's hmac.… and at.… tokens, in the app's order; none for the anonymous identity.

    configChecksum: PigeonChecksum

    The checksum of the config the server served the identity.

    deviceId: string
    familyId: string

    The device's family id: the second slot of the envelope's device ('' while the app does not know it).

    hmacTtlToken?: string

    The hmac_ttl.<issued>.<token> token the server issued the identity, as the device holds it (the expiry is kept but not acted on: spec/). The batch and the identity request carry it after the other tokens; the identity of a checksum entry never does.

    identityRequest: boolean

    Whether the upload asks the server to name the identity (the identity-request entry).

    pigeonSessionId: string
    samplingChecksum: PigeonChecksum

    The checksum of the sampling table the server served the identity.

    userId?: string

    The viewer's id; absent for the anonymous identity.