Retrieves all Runs for the specified connection.
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" 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.
"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.
Authorization header with valid Bearer token for scope
For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.
OAuth access token with scope
application/vnd.bentley.itwin-platform.v1+json is recommended.
Response 200 OK
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.
Response 403 Forbidden
This response indicates that user does not have required permissions to get specified connection runs.
Response 422 Unprocessable Entity
Invalid request to get connection.
Response 429 Too many requests
This response indicates that the user has sent too many requests in a given amount of time.
The number of requests exceeds the rate-limit for the client subscription.