POST /modelderivative/v2/designdata/{urn}/metadata/{modelGuid}/properties:query
Queries the objects in the Model View (Viewable) specified by the modelGuid parameter and returns the specified properties in a paginated list. You can limit the number of objects to be queried by specifying a filter using the query attribute in the request body.
Note: A design file must be translated to SVF or SVF2 before you can query object properties.
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 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.
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:
|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
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 |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
query |
Yes |
Specifies what objects to query. Contains the parameters to pass to the search service. You can use one of the following forms: |
|
pagination |
Object | Yes |
Specifies how to split the response into multiple pages, and return the response one page at a time. |
pagination.limit |
Number | Yes |
The maximum number of properties to return in a single page. Use this attribute with the |
pagination.offset |
Number | Yes |
The number of properties to skip. Use this attribute with the |
payload |
String | No |
Specifies the format for numeric values in the response body. Possible values:
Valid values:
|
fields |
Object | Yes |
Specifies what properties of the objects to return. If you do not specify this attribute, the response returns all properties. Possible values are:
|
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.