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

    Interface JsonHttpResponse<T>

    interface JsonHttpResponse<T = unknown> {
        body: T;
        delivery?: Readonly<Record<string, readonly number[]>>;
        headers: Record<string, string | string[]>;
        method: string;
        protocol?: string;
        status: number;
        statusMessage?: string;
        url: string;
    }

    Type Parameters

    • T = unknown

    Hierarchy

    Index

    Properties

    body: T
    delivery?: Readonly<Record<string, readonly number[]>>

    The document that first delivered each merged element of a chunked array (the merge's JsonStreamDelivery, by array key and element position): the one source of "which chunk an element came in", so a reader that groups entries by delivery does not decode the documents a second time — the feed's page decode groups its media checks by it (#960). Absent on an answer that is not a chunked stream (one document, GraphQL incremental delivery), where every element is the one document's.

    headers: Record<string, string | string[]>
    method: string
    protocol?: string

    Wire protocol the response actually came over, as reported by the native transport for this response: 'h3' (HTTP/3 over QUIC), 'h2' (HTTP/2 over TCP) or 'http/1.1'. It is the path the request really took, which can differ from the configured protocolMode: an iOS auto client whose QUIC attempt does not get through answers 'h2'. Absent when nothing was sent — responses produced by the render transport (createHttpRenderTransportLayer) or by a test transport. Typed as the transport's own string, so a value a newer transport adds passes through.

    status: number
    statusMessage?: string
    url: string