Get StorageConnection SourceFiles - Synchronization

REST API Overview

Reference

Changelog

Synchronization

Download API definition:

Get StorageConnection SourceFiles

GET https://api.bentley.com/synchronization/imodels/storageconnections/{connectionId}/sourcefiles[?$top][&$skip]

Retrieves SourceFiles for specified StorageConnection.

Notes

The Prefer header can be used to specify how much result metadata is desired by the client. The Prefer request header field is used to indicate that particular server behaviors are preferred by the client but are not required for successful completion of the request.

This operation supports "return=representation" and "return=minimal" preferences.

The "return=representation" preference indicates that the client prefers that the server include an entity representing the current state of the resource in the response to a successful request. The "return=minimal" preference indicates that the client wishes the server to return only a minimal response to a successful request. This is the default preference if Prefer header is not specified.

Authentication

Requires Authorization header with valid Bearer token for scope synchronization:read or itwin-platform.

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

Request

Request parameters

connectionId

template

Yes

Connection Id

$top

query

The $top system query option requests the number of items in the queried collection to be included in the result.

$skip

query

The $skip query option requests the number of items in the queried collection that are to be skipped and not included in the result.

Request headers

Authorization

Yes

OAuth access token with synchronization:read or itwin-platform scope

Yes

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

Response

Response 200 OK

json

{
    "sourceFiles": [{
            "id": "297c8ab9-53a3-4fe5-adf8-79b4c1a95cbb",
            "storageFileId": "t5bDFuN4qUa9ojVw1E5FGtldp8BgSbNCiJ2XMdiT-cA",
            "lastKnownFileName": "samplefile",
            "_links": {
                "file": {
                    "href": "https://api.bentley.com/files/t5bDFuN4qUa9ojVw1E5FGtldp8BgSbNCiJ2XMdiT-cA"
                }
            }
        },
        {
            "id": "5d22aa94-cde5-48ec-afcc-6c4aca67d51b",
            "storageFileId": "t5bDFuN4qUa9ojVw1E5FGtldp8BgSbNCiJ2XMdiT-cA",
            "lastKnownFileName": "samplefile",
            "_links": {
                "file": {
                    "href": "https://api.bentley.com/files/t5bDFuN4qUa9ojVw1E5FGtldp8BgSbNCiJ2XMdiT-cA"
                }
            }
        }
    ],
    "_links": {
        "self": {
            "href": "https://api.bentley.com/synchronization/imodels/storageconnections/{connectionId}/sourcefiles?$skip=100&$top=100"
        },
        "prev": {
            "href": "https://api.bentley.com/synchronization/imodels/storageconnections/{connectionId}/sourcefiles?$skip=0&$top=100"
        },
        "next": {
            "href": "https://api.bentley.com/synchronization/imodels/storageconnections/{connectionId}/sourcefiles?$skip=200&$top=100"
        }
    }
}

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 connection was not found.

json

{
    "error": {
        "code": "StorageConnectionNotFound",
        "message": "Requested StorageConnection is not available."
    }
}

Response 422 Unprocessable Entity

Invalid request to get connection sourcefiles.

json

{
    "error": {
        "code": "InvalidStorageConnectionSourceFilesRequest",
        "message": "Cannot perform operation.",
        "details": [{
            "code": "InvalidValue",
            "message": "Page size is out of limits.",
            "target": "$top"
        }]
    }
}

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

StorageFile (prefer return=minimal)

TableSchema

sourceFiles

storage-file-summary[]

A list of sourceFiles representing a minimal number of properties.

StorageFile (prefer return=representation)

TableSchema

sourceFiles

StorageFile[]

A list of sourceFiles representing all file properties.

StorageFile

TableSchema

String

Source file entity id.

storageFileId

String

Storage file id.

connectorType

connector-type

Type of connector used for synchronization. Refer supported connector format for details.

lastKnownFileName

String

Last known file name from data source.

_links

file-links

Link to the source file in storage API.

StorageFile (summary)

TableSchema

String

Source file entity id.

storageFileId

String

Storage file id.

lastKnownFileName

String

Last known file name from data source.

_links

file-links

Link to the source file in storage API.

File Links

TableSchema

file

Link

Link to associated file.

Link

TableSchema

href

String

Hyperlink to the specific entity.

Connector type

One of 'AUTOPLANT', 'CIVIL', 'CIVIL3D', 'DWG', 'GEOSPATIAL', 'IFC', 'MSTN', 'NWD', 'OBD', 'OPENTOWER', 'REVIT', 'SPPID', 'SPXREVIEW'. Name of the Connector that is used for synchronization.

TableSchema

No data.

Error

Contains error information.

TableSchema

code

String

One of a server-defined set of error codes.

message

String

A human-readable representation of the error.

target

String

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.

TableSchema

error

Error

Error information.