Table of contents
Synchronization
Download API definition:
POST https://dev-api.bentley.com/synchronization/imodels/storageconnections/{connectionId}/sourcefiles

Add a new Storage Source File to a Storage Connection

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.

Associated entities

SourceFile is added to a Connection. The reuqest path must contain a valid Connection ID

Request parameters

Name
Required?
Description
connectionId
Yes

Connection Id

Request headers

Name
Required?
Description
Authorization
Yes

OAuth access token with itwin-platform scope

Accept
Yes

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

Request body

StorageFile (create)

Name
Type
Required?
Description
storageFileId
String
Yes

Storage file id.

connectorType
Yes

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

Example

json
{
    "storageFileId": "t5bDFuN4qUa9ojVw1E5FGtldp8BgSbNCiJ2XMdiT-cA",
    "connectorType": "MSTN"
}

Response 201 Created

Storage Connection sourceFile successfully added.

json
{
    "sourceFile": {
        "id": "297c8ab9-53a3-4fe5-adf8-79b4c1a95cbb",
        "storageFileId": "t5bDFuN4qUa9ojVw1E5FGtldp8BgSbNCiJ2XMdiT-cA",
        "connectorType": "MSTN",
        "lastKnownFileName": "samplefile",
        "_links": {
            "file": {
                "href": "https://api.bentley.com/files/5db42812-ebb8-4c58-98a4-2eaa99e0d8b6"
            }
        }
    }
}

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 403 Forbidden

This response indicates that user does not have required permissions to create specified connection sourcefile.

json
{
    "error": {
        "code": "InsufficientPermissions",
        "message": "The user has insufficient permissions for the requested operation."
    }
}

Response 404 Not Found

This response indicates that the specified connection sourceFile was not found.

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

Response 409 Conflict

The SourceFile is already mapped to the iModel.

json
{
    "error": {
        "code": "FileMappingToTheIModelAlreadyExists",
        "message": "The SourceFile is already mapped to the iModel."
    }
}

Response 422 Unprocessable Entity

Invalid request to add connection sourcefile. Request payload might be missing some of the required properties.

json
{
    "error": {
        "code": "InvalidStorageConnectionSourceFileRequest",
        "message": "Cannot perform operation.",
        "details": [{
                "code": "InvalidRequestBody",
                "message": "Error parsing JSON, malformed JSON."
            },
            {
                "code": "MissingRequiredProperty",
                "message": "A property required to add or update  connection sourceFile is missing.",
                "target": "storageFileId"
            },
            {
                "code": "MissingRequiredProperty",
                "message": "A property required to add or update a connection sourceFile is missing.",
                "target": "connectorType"
            },
            {
                "code": "InvalidValue",
                "message": "connectorType must be one of: 'AUTOPLANT', 'CIVIL', 'CIVIL3D', 'DACQJSON', 'DWG', 'GEOSPATIAL', 'IFC', 'INTELLIPID', 'MSTN', 'NWD', 'OBD', 'OPENTOWER', 'PROSTRUCTURES', 'PSEXCEL', 'REVIT', 'SPPID', 'SPXREVIEW'.",
                "target": "connectorType"
            },
            {
                "code": "InvalidValue",
                "message": "Provided storageFileId value is not valid.",
                "target": "storageFileId"
            }
        ]
    }
}

Response 429 Too many requests

This response indicates that the client sent more requests than allowed by this API for the current tier of the client.

json
{
    "error": {
        "code": "RateLimitExceeded",
        "message": "The client sent more requests than allowed by this API for the current tier of the client."
    }
}

Response headers

Name
Description
retry-after

Number of seconds to wait until client is allowed to make more requests.

StorageFile response

Name
Type
Description
sourceFile

Storage file entity.

StorageFile

Name
Type
Description
id
String

Source file entity id.

storageFileId
String

Storage file id.

connectorType

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

lastKnownFileName
String

Last known file name from data source.

_links

Link to the source file in storage API.

StorageFile (create)

Name
Type
Description
storageFileId
String

Storage file id.

connectorType

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

File Links

Name
Type
Description
file

Link to associated file.

Link

Name
Type
Description
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.

Name
Type
Description
AUTOPLANT
String
CIVIL
String
CIVIL3D
String
DWG
String
GEOSPATIAL
String
IFC
String
MSTN
String
NWD
String
OBD
String
OPENTOWER
String
REVIT
String
SPPID
String
SPXREVIEW
String

Error

Contains error information.

Name
Type
Description
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.

Name
Type
Description
error

Error information.

Was this page helpful?