Postman Collection for Model Properties API

Description

This repository provides a postman collection that follows three tutorials for Model Properties API on APS developer portal. This API works with BIM360 Docs and Autodesk Docs.

The API supports 3 legged token only.

What's Postman?

Postman is a popular tool that provides an easy-to-use interface to send HTTP requests. Postman is able to parse the responses that APS sends you and save response parameter values to variables. These parameters can then be reused in subsequent requests through these variables. The Postman collections in this repository use this ability to provide pre-populated HTTP requests to help you follow the tutorial workflow with minimal effort. You can also modify the requests and experiment without having to write a single line of code.

• You can learn how to install and use Postman from here.

• You can download the Postman installer from here.

Setup

1. APS Account: Learn how to create a APS Account, activate the subscription and create an app by this tutorial. Get APS client id, client secret and callback url. Please register APS app with the callback url as

   https://www.getpostman.com/oauth2/callback

2. BIM 360 (or ACC) Account and project: must be Account Admin to add the app integration. Learn about provisioning. Make a note with the account name

3. Upload some demo models to one folder (better in any folder with Project Files). This Postman sample provides some Revit models. One model has two versions which can be used to test Diff API.

4. Get BIM 360/ACC Docs project id (without b.) by API , or copy from browser URL bar of Docs UI. And get the folder id.

5. Clone this repository or download it. It's recommended to install GitHub Desktop. To clone it via command line, use the following (Terminal on MacOSX/Linux, Git Shell on Windows):

   git clone https://github.com/autodesk-platform-services/aps-model.properties-postman.collection

6. Import the collection and environment files to Postman

7. In environment, input client id, client secret, project id, one folder id

   

8. In context menu of collection >> Edit, switch to the tab Authorization. Click Get New Access Token, input the variables as below:

   • Grant Type Authorization Code

   • Callback URL https://www.getpostman.com/oauth2/callback

   • Auth URL https://developer.api.autodesk.com/authentication/v1/authorize

   • Access Token URL https://developer.api.autodesk.com/authentication/v1/gettoken

   • Client ID {{client_id}}

   • Client Secret {{client_secret}}

   • Scope data:readx

   • Client Authentication Send Client credentials body

   

9. Click Get New Access Token, it will direct to login Autodesk account, after it succeeds, the token will be generated. Click Use Token.

Model Properties API requires to work with 3-legged token. This collection takes Inheriting auth to apply 3-legged token to every endpoint in the collection automatically, which means it does not need to input the token in the header explicitly.

API Test

1. Assume the steps of Setup have been performed and the access token is ready.

2. Play the scripts, following by the tutorials. Try to change some parameters or body for more scenarios to test.

   

Tutorial 1: Querying Model Properties

This follows the tutorial Querying Model Properties

0. GET Model Versions retrieves tip version urn of first and second model in the folder. You can also hard-coded the two urns in the variables: first_test_model_version, second_test_model_version

Follow the sequence of scripts to run the endpoints one by one. It will allow you to investigate one model version only. Check the indexing status, download manifest, fields, and raw properties data of the model. It will also let you post a query, and get the properties data which meet the query condition. Check the size and content of raw properties and query properties. Normally, raw properties have more data than query properties.

Tutorial 2: Tracking Changes in Model Versions

This follows the tutorial Tracking Changes in Model Versions

0. GET two versions of same model gets two version urn of one model in the folder. In the sample, the two versions of Audubon_Mechanical.rvt in Revit models are used. You can also hard-coded the two urns in the variables: prevVersionUrn, curVersionUrn

Run the sequence of script one by one. It will allow you to investigate how the diff works. Check the diff indexing status, download the manifest, fields, and raw properties data of the diff. It will also let you post a query, and get the properties data which meet the query condition. Check the size and content of raw properties and query properties. Normally, raw properties have more data than query properties.

Tutorial 3: Query Language Reference

This follows the tutorial Query Language Reference

0. GET one Model Version of Revit retrieves a tip version of urn for one Revit model in the folder. You can also hard-code the two urns with the variables: one_test_model_version

Run the sequence of script one by one. It will allow you to investigate one model version. Check the indexing status, download manifest, fields, and raw properties data of the model. It will also allow you to post one query (the 6th endpoint), and get the properties data which meet the query condition. Check the size and content of raw properties and query properties. It has one more query (also named 6th endpoint), run it, and repeat 7th, 8th endpoint to get query properties.

Notes

1. If the indexing is processing, wait a few minutes to check status again
2. If building query, please ensure the available fields contain the properties with which you want to build the query, and the correct property id (format looks like "p00723fa6")

Further Materials

• Model Properties API Reference
• Querying Model Properties
• Tracking Changes in Model Versions
• Query Language Reference
• Model Properties API Walkthrough in PowerShell Core

Blogs:

• APS Blog
• Field of View, a BIM focused blog

License

This sample is licensed under the terms of the MIT License. Please see the LICENSE file for full details.

Written by

Xiaodong Liang @coldwood, Developer Advovacy and Support, Autodesk