Runs the specified ExportConnection.
The export process usually takes time and is performed in the background. For that, we need to store the user's refresh token. The refresh token needs to be stored before calling the 'Create ExportConnection Run' end-point. You can get authorization information by using Get Authorization Information API. This API will return the current status and a redirect URL if the token has to be renewed.
When a run is successfully created, the operation returns HTTP status code 202/accepted - the request is accepted for processing and will execute in background. The response will include a location header pointing to the created run. If an existing active run already exists for the iModel, a new run is not initiated, instead 303/see other is returned along with location header pointing to that existing active run. In the rare event that multiple create run requests are being made simultaneously, only the first request is processed and 409/conflict is returned for others.
Authorization header with valid Bearer token for scope
For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.
This response indicates that an active run is in progress and link is provided in location header.
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.
This response indicates that user does not have required permissions to run specified connection.
This response indicates that the specified connection not found.
A run request is already being processed.
Invalid request to create a connection run.
One of 'IFC', 'LandXML'. Name of the file type to export to.
If the exportType is 'IFC', ifcVersion must be one of 'IFC4.3 RC1', 'IFC2x3', 'IFC2x3 CV 2.0', 'IFC4 RV 1.2'.
One of 'USER_BLOB_STORAGE', 'STORAGE'. Type of location to export to. Default is 'STORAGE' (Storage API).
Contains error information.
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.