Get StorageConnection Runs - Synchronization

REST API Overview

Reference

Changelog

Synchronization

Download API definition:

Get StorageConnection Runs

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

Retrieves all Runs for the specified connection.

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 itwin-platform.

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

Request

Request parameters

connectionId

Yes

Connection Id

$top

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

$skip

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 itwin-platform scope

Yes

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

Response

Response 200 OK

json

{
    "runs": [{
        "id": "a1ecbdc8c4f6173004f9f881914a57c5511a362b",
        "state": "Completed",
        "result": "PartialSuccess"
    }],
    "_links": {
        "self": {
            "href": "https://api.bentley.com/synchronization/imodels/connection/{connectionId}/runs?$skip=100&$top=100"
        },
        "prev": {
            "href": "https://api.bentley.com/synchronization/imodels/connection/{connectionId}/runs?$skip=0&$top=100"
        },
        "next": {
            "href": "https://api.bentley.com/synchronization/imodels/connection/{connectionId}/runs?$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 not found.

json

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

Response 422 Unprocessable Entity

Invalid request to get connection.

json

{
    "error": {
        "code": "InvalidStorageConnectionRunsRequest",
        "message": "Cannot perform operation.",
        "details": [{
                "code": "InvalidValue",
                "message": "Page size is out of limits.",
                "target": "$top"
            },
            {
                "code": "InvalidValue",
                "message": "Provided connectionId value is not valid.",
                "target": "connectionId"
            }
        ]
    }
}

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

Runs (prefer return=minimal)

runs

run-summary[]

A set of storage run entities representing a minimal number of properties.

Run error details

errorKey

String

Error key.

description

String

More information about run error.

Runs (prefer return=representation)

runs

storage-run[]

A set of storage run entities representing all storage run properties.

storage-run

String

A connection run id.

connectionId

String

Connection id.

startDateTime

String

A timestamp when connection run started.

endDateTime

String

A timestamp when connection run ended.

phase

job-phase

Job phase.

state

execution-state

A string indicating current execution status of the run.

result

execution-result

A string indicating outcome of the executed run.

error

run-error-details

Run error entity.

jobs

storage-job[]

An array of storage job entities.

storage-job

String

A storage job id.

startDateTime

String

A timestamp when storage job started.

endDateTime

String

A timestamp when storage job ended.

state

String

A string indicating current execution status of the job.

result

String

A string indicating outcome of the executed job.

connectorType

connector-type

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

tasks

storage-task[]

An array of storage task entities.

storage-task

String

A storage task id.

startDateTime

String

A timestamp when storage task started.

endDateTime

String

A timestamp when storage task ended.

retryAttempts

Integer

The number of attempts when storage task was retried.

storageFileId

String

Storage file id.

state

String

A string indicating current status of the storage task.

result

String

A string indicating outcome of the storage task.

error

task-error

Task error entity.

details

task-details

Task result details.

Job Phase

One of 'Preprocessor', 'MasterFile', 'ReferenceFile'.

Preprocessor

String

MasterFile

String

ReferenceFile

String

Execution State

One of 'NotStarted', 'Idle', 'WaitingToExecute', 'WaitingToRetry', 'Executing', 'Finalizing', 'Completed', 'Queued'.

NotStarted

String

Idle

String

WaitingToExecute

String

WaitingToRetry

String

Executing

String

Finalizing

String

Completed

String

Queued

String

Execution Result

One of 'Undetermined', 'Success', 'Error', 'PartialSuccess', 'Skipped', 'Canceled', 'TimedOut'.

Undetermined

String

Success

String

Error

String

PartialSuccess

String

Skipped

String

Canceled

String

TimedOut

String

Run (summary)

String

A run id.

state

String

A string indicating current status of the run.

result

String

A string indicating outcome of the run.

task-error

errorCode

String

Error code.

message

String

A human-readable representation of the error.

details

String

More specific information about the error.

bridgeExitCode

Integer

An integer representing connector exit code.

system

String

System.

phase

String

Phase.

Task details

SynchronizationReport

synchronization-report

Synchronization result summary

Synchronization report

suggestedAction

suggested-action

Most severe issue type

message

String

Error message explaining the result

totalErrorsCount

Integer

Number of errors in the report

totalWarningsCount

Integer

Number of warnings in the report

totalOtherIssuesCount

Integer

Number of other issues in the report

Suggested action

Error severity level

Error

String

Warning

String

Info

String

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.

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.

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.