GET /modelderivative/v2/designdata/{urn}/metadata/{modelGuid}/properties
Returns a list of properties of all objects in the Model View specified by the modelGuid parameter.
This operation returns properties of all objects by default. However, you can restrict the results to a specific object by specifying its ID as the objectid parameter.
Properties are returned as a flat list, ordered, by their objectid. The objectid is a non-persistent ID assigned to an object when the source design is translated to the SVF or SVF2 format. This means that:
- A design file must be translated to SVF or SVF2 before you can retrieve properties.
- The
objectidof an object can change if the design is translated to SVF or SVF2 again. If you require a persistent ID across translations, useexternalIdto reference objects, instead ofobjectid.
Before you call this operation:
- Use the
List Model Views </en/docs/model-derivative/v2/reference/http/metadata/urn-metadata-GET/>_ operation to obtain the list of Model Views (Viewables) in the source design. - Pick the ID of the Model View you want to query and specify that ID as the value for the
modelGuidparameter.
Tip: Use Fetch Specific Properties </en/docs/model-derivative/v2/reference/http/metadata/urn-metadata-guid-properties-query-POST/>_ to retrieve only the objects and properties of interest. What’s more, the response is paginated. So, when the number of properties returned is large, responses start arriving more promptly.
Servers
- https://developer.api.autodesk.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
modelGuid |
String | Yes |
The ID of the Model View you are querying. Use the |
urn |
String | Yes |
The URL-safe Base64 encoded URN of the source design. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
x-ads-derivative-format |
String | No |
Specifies what Object IDs to return, if the design has legacy SVF derivatives generated by the BIM Docs service. Possible values are:
Note:
Valid values:
|
region |
String | No |
Specifies the data center where the manifest and derivatives of the specified source design are stored. Possible values are:
Valid values:
|
x-ads-force |
Boolean | No |
|
Accept-Encoding |
String | No |
A comma separated list of the algorithms you want the response to be encoded in, specified in the order of preference. If you specify |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
forceget |
String | No |
|
objectid |
Integer | No |
The Object ID of the object you want to restrict the response to. If you do not specify this parameter, all properties of all objects within the Model View are returned. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.