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

    Response envelope returned by Bloks-aware HTTP services.

    body is the raw UTF-8 response body as a string — kept unparsed because the only remaining use case is substring containment checks (error markers, throttle messages). For structured access use dicts/literals, which come from the opcode-agnostic Rust extractor.

    All four properties are lazy getters — reading body doesn't decode the extract and vice versa, so consumers pay only for what they touch.

    interface BloksResponse {
        ast: readonly Bloks.BloksAstNode[];
        body: string;
        dicts: readonly Bloks.BloksDict[];
        json: unknown;
        jsonLiterals: readonly Record<string, unknown>[];
        literals: readonly Bloks.BloksLiteral[];
    }

    Hierarchy (View Summary)

    Index

    Properties

    ast: readonly Bloks.BloksAstNode[]
    body: string
    dicts: readonly Bloks.BloksDict[]
    json: unknown

    The body as a parsed JSON value, read by the core's one reader after the tolerant repair (parseJSON): the code outside the core never parses JSON text, it reads this. A body that is not JSON is undefined (no JSON text reads as undefined, so it is told from a body that is null). Lazy, read once, and never enumerable: a spread, Object.entries or a serialisation of the response does not read it.

    jsonLiterals: readonly Record<string, unknown>[]
    literals: readonly Bloks.BloksLiteral[]