Retrieves the metadata of a Changeset.
For more information on creating and retrieving Changesets using iTwin.js see working with Changesets.
Authorization header with valid Bearer token for scope
For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.
User must have
imodels_webview permission assigned at the iModel level and at least
imodels_webview permission assigned at the iTwin level. If permissions at the iModel level are not configured, then user must have
imodels_webview permission assigned at the iTwin level.
Alternatively the user should be an Organization Administrator for the Organization that owns a given iTwin the iModel belongs to.
An Organization Administrator must have at least one of the following roles assigned in User Management: Account Administrator, Co-Administrator, or CONNECT Services Administrator. For more information about User Management please visit our Bentley Communities Licensing, Cloud, and Web Services wiki page.
download property requires user to have at least
imodels_read permission. If user has only
download will always be null.
All iTwin Platform API operations have a rate limit. For more documentation on that visit Rate limits and quotas page.
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.
Specified iModel or Changeset was not found.
Container for Changeset object.
Changeset represents a file containing changes to the iModel. A single Changeset contains changes made on a single Briefcase file and pushed as a single file.
Hyperlinks to Changeset related data.
Information about the client application that is related to an entity.
Information about synchronization that is related to a Changeset. This information is set by applications that perform iModel synchronization.
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.