Get issue attachments - Issues

REST API Overview

Reference

Issues

Download API definition:

GET https://qa-api.bentley.com/issues/{id}/attachments

Retrieves the metadata for all files attached to the given issue. In order to get the contents of a file itself, use the Get attachment file by ID endpoint, passing the id from the metadata object returned by this request as the attachmentId parameter of that request.

Permissions

To use this endpoint, the user is required to have the Forms View (Forms_ViewAccess) permission for the iTwin, or for the issue's associated form definition if form definition security is specified. (Having any other level of Forms permission automatically grants the View permission as well.)

Authentication

Requires Authorization header with valid Bearer token for scope itwin-platform.

For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.

Request

Request parameters

Yes

The ID of the issue to get attachments for

Request headers

Authorization

Yes

OAuth access token with itwin-platform scope

Yes

Setting to application/vnd.bentley.itwin-platform.v1+json is recommended.

Response

Response 200 OK

json

{
    "attachments": [{
            "id": "XZzxOCC8sVvUcgeXz1Ih_exlLgPfRTpAuShXz1cTpAu",
            "fileName": "CrackedConcrete.png",
            "createdDateTime": "2020-10-20T16:16:30.6704320Z",
            "size": 34770,
            "caption": "Picture of the cracked concrete",
            "binding": "TypeOfDefect",
            "type": "png"
        },
        {
            "id": "XZzxOCC8sVvUcgeXz1Ih_exlLgPfRTpAuShXz1cTpAu",
            "fileName": "StreetView.png",
            "createdDateTime": "2020-10-20T16:08:30.2804722Z",
            "size": 56893,
            "caption": "Picture showing the bridge from the perspective of an approaching car",
            "binding": null,
            "type": "png"
        }
    ]
}

Response 401 Unauthorized

This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.

json

{
    "error": {
        "code": "HeaderNotFound",
        "message": "Header Authorization was not found in the request. Access denied."
    }
}

Response 404 Not Found

This response indicates that the specified issue does not exist or is inaccessible to the user.

json

{
    "error": {
        "code": "IssueNotFound",
        "message": "Requested issue is not available.",
        "target": "id"
    }
}

Response 429 Too many requests

This response indicates that the user has sent too many requests in a given amount of time.

json

{
    "error": {
        "code": "TooManyRequests",
        "message": "More requests were received than the subscription rate-limit allows."
    }
}

Response headers

retry-after

The number of requests exceeds the rate-limit for the client subscription.

Definitions

Attachment Metadata List

attachments

attachment-metadata-get[]

Attachment Metadata (get)

String

Read-only. String that uniquely identifies this attachment and can be used in the Get attachment file by ID request to download the file.

fileName

String

The name of the file that was uploaded.

type

String, null

Read-only. File extension of the uploaded file. Derived from fileName.

caption

String, null

Descriptive string provided by a user for this attachment, if any.

createdDateTime

Date-time

Date and time the attachment was uploaded. Read-only; auto-set when attachment is created.

size

Integer, null

Size of the file in bytes. Read-only; auto-set when attachment is uploaded.

binding

String, null

If the attachment was uploaded from an Image Drop control, this is the property name the control is bound to. Otherwise, null.

Error

Contains error information.

code

String

One of a server-defined set of error codes.

message

String

A human-readable representation of the error.

target

String, null

The target of the error.

Error Response

Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.

error

Error

Error information.