Navigation
VigilbaseDocs

    Type at least two letters.

    Open Vigilbase One

    Get a message attachment

    One file on a support request message (GET /api/support/tickets/{issueId}/messages/{messageId}/attachments/{index}). Same access as the thread: the issue must belong to the session's (or, for staff, the named) customer's Pylon account, and customers only reach files on customer-visible messages. The file is streamed from Pylon's file host; its signed link is never sent to the browser. Photos are served inline for previews; everything else, or any request with ?download=1, downloads.

    GET/api/support/tickets/{issueId}/messages/{messageId}/attachments/{index}

    Authorizations

    Send one of these:

    AuthorizationstringAccess tokenheaderrequired

    Bearer access token from Vigilbase Identity (auth.vigilbase.com), sent as Authorization: Bearer <token>. The CLI gets one with vigilbase login.

    AuthorizationstringAPI keyheaderrequired

    Organisation API key (vb_one_…) from Settings → API keys in Vigilbase One, sent as Authorization: Bearer vb_one_…. Read-only keys work. See organisation API keys.

    Permissions checkedsupport:access

    Path Parameters

    issueIdstringrequired
    messageIdstringrequired
    indexstringrequired

    Query Parameters

    customerIdstringuuid
    downloadstring
    Value:1

    Response

    Success

    Was this page helpful?