IGPAPI
    Preparing search index...

    Interface MessengerMediaUploadInput

    interface MessengerMediaUploadInput {
        entityName: string;
        entityParams?: HttpHeaders;
        entityType: string;
        file: Buffer;
        fileName?: string;
        openSlot: boolean;
        path: string;
        uploadParams?: HttpHeaders;
    }
    Index

    Properties

    entityName entityParams? entityType file fileName? openSlot path uploadParams?

    Properties

    entityName: string

    The entity's name, sent as x-entity-name.

    entityParams?: HttpHeaders

    Params the app sends on both the slot's GET and the file's POST — the media kind (image_type / audio_type / video_type) and a video's waterfall and segment type.

    entityType: string

    The entity's content type, sent as x-entity-type.

    file: Buffer
    fileName?: string

    The file name the URL ends with, when it is not the entity name: the Direct disappearing photo names its entity by the upload id and its URL <upload id>_0_<random>.

    openSlot: boolean

    Whether the app opens an upload slot (GET to the same URL) before it posts the file. It is a property of the upload kind, not a step every upload shares: the recorded voice message opens it (Android 448 recording) and the video kinds follow that shape, while the photo kinds and the wallpaper post the file straight away — the only observed messenger_image wire is a POST with no slot (a live run). The caller states it per kind and nothing defaults it.

    path: string

    The upload path, e.g. messenger_image, messenger_audio, messenger_video.

    uploadParams?: HttpHeaders

    Params only the file's POST carries (segment-start-offset, the Direct flags).

    Settings

    Member Visibility

    On This Page

    Properties