reality-data-metadata

Identifier of the reality data. This identifier is assigned by the service at the creation of the reality data. It is also unique.

string

The name of the reality data. This property may not contain any control sequence such as a URL or code.

displayName

This field can be used to define a loose grouping of reality data. This property may not contain any control sequence such as a URL or code.

dataset

The group can be used to define a second level of grouping. This property may not contain any control sequence such as a URL or code.

group

A textual description of the reality data. This property may not contain any control sequence such as a URL or code.

description

Any string identifier which you can assign to reality data to identify it.

array

Used to indicate the root document of the reality data. The root document can be in a subfolder and is then specified as “Tile_Root.json” or “Folder1/SubFolder1/File.json” for example.

rootDocument

The size of the reality data in Kilobytes.

size

int64

Specific value constrained field that indicates the nature of the reality data. The following values are currently supported: Terrain, Imagery, Pinned, Model, Undefined.

classification

A key indicating the format of the data. The type property should be a specific indication of the format of the reality data. Given a type, the consuming software should be able to determine if it has the capacity to open the reality data. Although the type field is a free string some specific values are reserved and other values should be selected judiciously. Look at the documentation for an exhaustive list of reserved [reality data types](/apis/reality-management/rm-rd-details/#types).

type

Provides information regarding the acquisition, such as dates and acquirer used.

acquisition

Contains the rectangular area on the Earth which encloses the reality data.

extent

A boolean value that is true if the data is being created. It is false if the data has been completely uploaded.

authoring

boolean

Identifies the data center location used to store the reality data.

dataCenterLocation

ISO-8601 compliant time (UTC) of last modification of the reality data. E.g. '2017–05–10T13:43:03Z'

modifiedDateTime

date-time

ISO-8601 compliant time (UTC) of last access of the reality data. E.g. '2017–05–10T13:43:03Z'

lastAccessedDateTime

ISO-8601 compliant time (UTC) of the creation of the reality data. E.g. '2017–05–10T13:43:03Z'

createdDateTime

Identifier of the owner of the reality data.

ownerId

Reality Data Details

reality-data-metadata-response

realityData

Reality Data Metadata Response

reality-data-metadata-create-response

Reality Data Details Response

ISO-8601 compliant time (UTC) that indicates when the data acquisition started. E.g. '2017-05-10T13:43:03Z'

startDateTime

ISO-8601 compliant time (UTC) that indicates when the data acquisition ended. E.g. '2017-05-10T13:43:03Z'

endDateTime

acquirer

Acquisition

Extent of a reality data, delimited by southwest and northeast coordinates.

southWest

coordinate

northEast

Extent

Latitude. Latitude ranges between -90 and 90 degrees, inclusive.

latitude

double

Longitude. Longitude ranges between -180 and 180 degrees, inclusive.

longitude

Coordinate

request-body-create

iTwinId

Specific value constrained field that indicates the nature of the reality data. Allowed values: 'Terrain', 'Imagery', 'Pinned', 'Model', 'Undefined'

A key indicating the format of the data. Valid values include '3MX', 'PointCloud', RealityMesh3DTiles', ... See documentation for an exhaustive list of registered [reality data types](/apis/reality-management/rm-rd-details/#types).

Used to indicate the root document of the reality data.

The rectangular area on the Earth which encloses the reality data.

Reality Data

Ids of associated iTwin and reality data.

iTwin-association-response

iTwinAssociation

iTwin-association

iTwin Association Response

Defines an association between a reality data and a iTwin

iTwin Association

link

href

List of all iTwins associated to a reality data.

reality-data-iTwins-response

iTwins

List of iTwins Associated to a Reality Data

get-access-to-container-response

Type of container. Currently, only 'AzureBlobSasUrl' is supported.

access

_links

container-links

Container Details Response

Provides a link and other details for a reality data container

container-details

Container Details

containerUrl

container-url

Container Links

Container URL

reality-data-self-link

The link to get the reality data details.

self

Reality Data Details Link

reality-data-metadata-summary

reality-data-metadata-return-minimal

next-page-link

reality-data-metadata-return-representation

URL for getting the next page of data, if applicable.

Next Page Link

Request body for updating a reality data.

request-body-update

Reality Data (Update)

Contains error information and an array of more specific errors.

DetailedError

One of a server-defined set of error codes.

code

A human-readable representation of the error.

message

target

details

Error

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.

DetailedErrorResponse

error

Detailed Error Response

ErrorResponse

Error Response

AcceptHeader

AuthorizationHeader

PreferHeader

return=representation

return=minimal

Interact with your reality data.

View, update, create, and delete reality data.


reality-management

---

Associates a [reality data](https://www.itwinjs.org/learning/glossary/#realitydata) to a iTwin.

### 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](https://developer.bentley.com/apis/overview/authorization/) page.

### Authorization

User must have the `realitydata_create , realitydata_assign` permission assigned at the iTwin level or be an Organization Administrator for the Organization that owns a given iTwin.

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](https://bentleysystems.service-now.com/community?id=kb_article_view&sys_kb_id=1e5410491b7d8a90f3fc5287624bcb57) wiki page.

### Rate limits

All iTwin Platform API operations have a rate limit. For more documentation on that visit [Rate limits and quotas](https://developer.bentley.com/apis/overview/rate-limits/) page.

---

associate-to-iTwin

OAuth access token with `itwin-platform` scope

Authorization

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

Accept

Reality data successfully associated to the iTwin

default

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.

HeaderNotFound

InvalidAuthorizationScheme

InvalidHeaderValue

RequiredScopeMissing

Unauthorized

InvalidApplicationTier

The user has insufficient permissions for the requested operation.

This response indicates that the reality data id or the iTwin id was not found.

This response indicates that the Association with the same iTwin already exists.

Invalid request to associate reality data to iTwin. Please ensure that the request is valid.

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.

retry-after

---

Dissociates a [reality data](https://www.itwinjs.org/learning/glossary/#realitydata) from a iTwin.

### 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](https://developer.bentley.com/apis/overview/authorization/) page.

### Authorization

User must have the `realitydata_create , realitydata_assign` permission assigned at the iTwin level or be an Organization Administrator for the Organization that owns a given iTwin.

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](https://bentleysystems.service-now.com/community?id=kb_article_view&sys_kb_id=1e5410491b7d8a90f3fc5287624bcb57) wiki page.

### Rate limits

All iTwin Platform API operations have a rate limit. For more documentation on that visit [Rate limits and quotas](https://developer.bentley.com/apis/overview/rate-limits/) page.

---

dissociate-from-iTwin

This response indicates that user does not have required permissions to dissociate a reality data from iTwin.

This response indicates that the association between the reality data and iTwin was not found.

Invalid request to dissociate reality data from iTwin. Please ensure that the request is valid.

---

Retrieves the list of iTwins associated to the specified [reality data](https://www.itwinjs.org/learning/glossary/#realitydata).

When no iTwin is associated to the reality data, an empty list is returned.

### 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](https://developer.bentley.com/apis/overview/authorization/) page.

### Authorization

User must have the `realitydata_use` permission assigned at the iTwin level or be an Organization Administrator for the Organization that owns a given iTwin.

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](https://bentleysystems.service-now.com/community?id=kb_article_view&sys_kb_id=1e5410491b7d8a90f3fc5287624bcb57) wiki page.

### Rate limits

All iTwin Platform API operations have a rate limit. For more documentation on that visit [Rate limits and quotas](https://developer.bentley.com/apis/overview/rate-limits/) page.

---

get-reality-data-iTwins

This response indicates that user does not have required permissions to get iTwins for a reality data.

This response indicates that the requested reality data was not found.

Invalid request to get iTwins for reality data. Please ensure that the request is valid.


---
Retrieves the container's link with read access for an instance of [reality data](https://www.itwinjs.org/learning/glossary/#realitydata).

A container is where the reality data itself (a point cloud, a mesh, a collection of images, ...) is stored.

The container's link will allow you to upload/download data directly to this container.

A [reality data](https://www.itwinjs.org/learning/glossary/#realitydata) is always associated to exactly one container.

The `iTwinId` parameter is optional, but it is preferable to provide it, because the permissions used to access the container are determined from the iTwin. With no iTwin specified, the operation can succeed in some cases (e.g. the user is the reality data's owner), but we recommend to provide a `iTwinId`.

In future API versions, containers could be hosted in in different cloud providers, but for now, only Azure cloud is supported.

To store or retrieve data from a container, refer to the [Azure Blob Storage documentation](https://docs.microsoft.com/en-us/azure/storage/blobs/).

### 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](https://developer.bentley.com/apis/overview/authorization/) page.

### Authorization
User must be an Organization Administrator for the Organization that owns a given iTwin or have realitydata_use permission for read access assigned at the iTwin level.

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.

### Rate limits

All iTwin Platform API operations have a rate limit. For more documentation on that visit [Rate limits and quotas](https://developer.bentley.com/apis/overview/rate-limits/) page.

---


get-read-access-to-reality-data-container

This response indicates that user does not have required permissions.

This response indicates that the reality data not found.

Invalid request to get access to reality data.. Please ensure that the request is valid.


---
Retrieves the container's link with write access for an instance of [reality data](https://www.itwinjs.org/learning/glossary/#realitydata).

A container is where the reality data itself (a point cloud, a mesh, a collection of images, ...) is stored.

The container's link will allow you to upload/download data directly to this container.

A [reality data](https://www.itwinjs.org/learning/glossary/#realitydata) is always associated to exactly one container.

The `iTwinId` parameter is optional, but it is preferable to provide it, because the permissions used to access the container are determined from the iTwin. With no iTwin specified, the operation can succeed in some cases (e.g. the user is the reality data's owner), but we recommend to provide a `iTwinId`.

In future API versions, containers could be hosted in in different cloud providers, but for now, only Azure cloud is supported.

To store or retrieve data from a container, refer to the [Azure Blob Storage documentation](https://docs.microsoft.com/en-us/azure/storage/blobs/).

### 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](https://developer.bentley.com/apis/overview/authorization/) page.

### Authorization
User must be an Organization Administrator for the Organization that owns a given iTwin or have realitydata_manage permission for write access assigned at the iTwin level.

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.

### Rate limits

All iTwin Platform API operations have a rate limit. For more documentation on that visit [Rate limits and quotas](https://developer.bentley.com/apis/overview/rate-limits/) page.

---


get-write-access-to-reality-data-container

Invalid request to get access to reality data. Please ensure that the request is valid.

---

Creates a [reality data](https://www.itwinjs.org/learning/glossary/#realitydata).

As shown in the request section below, you must provide a request body.

You MUST provide the `displayName` and `type` properties.

The `rootDocument` property is not required but highly recommended. It is the entry point for consuming applications to read the content of the Reality Data. [See RootDocument property](https://developer.bentley.com/apis/reality-management/rm-rd-details/#root-document)

For more details on each property, see [Reality Data Properties](https://developer.bentley.com/apis/reality-management/rm-rd-details/) in documentation.

After creation, the reality data will be associated to the specified iTwin.

### 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](https://developer.bentley.com/apis/overview/authorization/) page.

### Authorization

User must have the `realitydata_create` permission assigned at the iTwin level or be an Organization Administrator for the Organization that owns a given iTwin.

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](https://bentleysystems.service-now.com/community?id=kb_article_view&sys_kb_id=1e5410491b7d8a90f3fc5287624bcb57) wiki page.

### Rate limits

All iTwin Platform API operations have a rate limit. For more documentation on that visit [Rate limits and quotas](https://developer.bentley.com/apis/overview/rate-limits/) page.

---

create-reality-data

This response indicates that user does not have required permissions to create a reality data.

Invalid request to create reality data. Please ensure that the request is valid.

application/json;InvalidRealityDataRequest

InvalidRealityDataRequest

MissingRequestBody

---

Deletes a [reality data](https://www.itwinjs.org/learning/glossary/#realitydata).

To delete a reality data, it must be associated to only one (or zero) iTwin. If it has more associated iTwins, first [dissociate](https://developer.bentley.com/apis/reality-management/operations/dissociate-from-itwin/) the iTwins.

### 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](https://developer.bentley.com/apis/overview/authorization/) page.

### Authorization

User must have the `realitydata_manage` permission assigned at the iTwin level or be an Organization Administrator for the Organization that owns a given iTwin.

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](https://bentleysystems.service-now.com/community?id=kb_article_view&sys_kb_id=1e5410491b7d8a90f3fc5287624bcb57) wiki page.

### Rate limits

All iTwin Platform API operations have a rate limit. For more documentation on that visit [Rate limits and quotas](https://developer.bentley.com/apis/overview/rate-limits/) page.

---

delete-reality-data

This response indicates that the specified reality data was not found.

Invalid request to delete reality data. Please ensure that the request is valid.

---

Retrieves a list of [reality data](https://www.itwinjs.org/learning/glossary/#realitydata) instances belonging to the specified iTwin.

The retrieved instances are those for which you have the required access rights, relative to the specified iTwin. 

The `iTwinId` is optional. If you don't provide it, the retrieved [reality data](https://www.itwinjs.org/learning/glossary/#realitydata) instances will be relative to general access rights provided by your organization. These rights are usually more restrictive, so we recommend using the `iTwinId` parameter for exhaustive results.

### 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, i.e., all properties are included in the response.
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](https://developer.bentley.com/apis/overview/authorization/) page.

### Authorization

User must be an Organization Administrator for the Organization that owns a given iTwin or must have access to context.

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.

### Rate limits

All iTwin Platform API operations have a rate limit. For more documentation on that visit [Rate limits and quotas](https://developer.bentley.com/apis/overview/rate-limits/) page.

---

get-all-reality-data

Id of iTwin. The operation gets all reality data in this iTwin.

Parameter that enables continuing to the next page of the previous paged query. This must be passed exactly as it is in the response body's _links.next property. If this is specified and $top is omitted, the next page will be the same size as the previous page.

continuationToken

The number of reality data to get in each page. Max 1000, but 100 is the default if this parameter is not included.

$top

Extent of the area to search, delimited by southwest and northeast coordinates. Extent values are specified in this format: SouthwestCorner_Longitude, SouthwestCorner_Latitude, NortheastCorner_Longitude, NortheastCorner_Latitude. E.g. to get all reality data in an area around Exton, PA, provide the following extent parameter: extent=-75.637679,40.032871,-75.633647,40.032771

Parameter that enable to order reality data in ascending or descending order. Default is ascending.Example : displayName desc

$orderBy

$search

Comma separated list of reality data types. Example: "OPC,Terrain3DTiles, OMR, Cesium3DTiles" 

types

Aquisition datetime range in ISO-8601 compliant time (UTC).
Format: startDateTime/endDateTime
Example: 2021-05-12T20:03:12Z/2022-05-12T20:03:12Z

acquisitionDateTime

Created datetime range in ISO-8601 compliant time (UTC).
Format: startDateTime/endDateTime
Example: 2021-05-12T20:03:12Z/2022-05-12T20:03:12Z

Modified datetime range in ISO-8601 compliant time (UTC).
Format: startDateTime/endDateTime
Example: 2021-05-12T20:03:12Z/2022-05-12T20:03:12Z

API references