Skip to content
This repository has been archived by the owner on Nov 28, 2023. It is now read-only.

Latest commit

 

History

History

BIM360 Assets API Step-by-Step Tutorial

Platforms oAuth2 Data-Management BIM360-Assets

Postman

Beginner License

This folder contains a Postman Collection that includes the requests covering the current main workflow of BIM360 Assets. The collection together with the environment shows you how to use Assets API. It includes Retrieve BIM 360 Account and Project ID, Setup BIM 360 Assets Settings, Create BIM 360 Assets Data, and Retrieve BIM 360 Assets Data.

Collection

Demonstration

https://youtu.be/2u3kSjm-XEo

Click here or click on the above picture to view the video

Preparation before you begin:

Instructions to run the Postman tutorial are as below:

Please watch the Video for the detail workflow, or follow the steps:

Setup Postman environment and Authorization:

Tutorials of BIM360 Assets workflow

  • Retrieve BIM 360 Account and Project ID: It contains a set of Postman scripts demonstrating how to obtain your BIM 360 Account and Project ID. If you already have these, you can skip this tutorial.

    • Step 1: List all the Hubs, specify the hub_name in Pre-request Script which you want to work with, then save hub_id for the 1st BIM360 Hub, also save account_id. (Data Management API)
    • Step 2: List all the projects in the BIM360 Hub, specify the project_name in Pre-request Script which you want to work with, then get project_id for the specified project and save it. Also, save assets_project_id. (Data Management API)
  • Setup BIM 360 Assets Settings: It contains a set of Postman scripts demonstrating how to set up a new BIM 360 project's Asset settings.

    • Step 1: Create Categories
      • Step 1.1: List all the categories of BIM 360 Assets, and save asset_category_parent_id of the ROOT category for creating a new category under it. (Assets API)
      • Step 1.2: Create a new asset category with the value of the asset_category_name specified in the Pre-request Script. Save asset_category_id for the category you just created. (Assets API)
    • Step 2: Create Status Sets and Statuses
      • Step 2.1: Create a new Asset status set with the value of the asset_status_set_name specified in the Pre-request Script. Save asset_status_step_set_id for the Asset status set you just created. (Assets API)
      • Step 2.2: Create a new Asset status and append it to the status set created in Step 2.1. Save asset_status_id for the Asset status you just created. (Assets API)
    • Step 3: Assign Status Sets created in Step 2 to the category of Step 1. (Assets API)
    • Step 4: Create a new custom attribute of the BIM 360 Assets with the value of the custom_attribute_displayname specified in the Pre-request Script. Save custom_attribute_id and custom_attribute_name for the asset you just created. (Assets API)
    • Step 5: Assign Custom Attributes created in Step 4. to the category of Step 1. (Assets API)
    • Step 6: Assign Checklists to Categories
      • Step 6.1: Get the information of the specified BIM360 project, and save issues_container_id for the Issues Container(Data Management API).
      • Step 6.2: Get all available checklist templates, save checklist_template_id of the first checklist template for associating it with the assets. (Checklists API)
      • Step 6.3: Associate the checklist template of Step 13 with the category created in Step 4. (Assets API)
  • Managing BIM 360 Assets Data: It contains a set of Postman scripts demonstrating how to create Asset data, work with Issue API to crate an issue, and assign the issue to an asset.

    • Step 1: Create new Assets
      • Step 1.1: Get all available asset categories, save asset_category_id of the last one for creating new assets. (Assets API)
      • Step 1.2: Get asset status sets assigned to category ids, save asset_status_set_id of the first one for obtaining asset statuses. (Assets API)
      • Step 1.3: Get asset statuses under given status set ids, save asset_status_id of the first value of first status set for creating new assets. (Assets API)
      • Step 1.4: Create a new asset with the value of the asset_name specified in the Pre-request Script. Save asset_id for the asset you just created. (Assets API)
    • Step 2: Update Existing Assets
      • Step 2.1: Get all available custom attributes assign to the category, find a text-typed custom attribute, and save custom_attribute_id and custom_attribute_name for updating custom attributes' value. (Assets API)
      • Step 2.2: Update custom attribute value to Hello World! (Assets API)
    • Step 3: Fetch Existing Assets of the specified BIM360 project (Assets API)
    • Step 4: Assign Issues to Assets
      • Step 5.1: Get the information of the specified BIM360 project, and save issues_container_id for the Issues Container. (Data Management API)
      • Step 5.2: Get all available issue types and subtypes, save issue_type of the first issue type and its first subtype as issue_subtype for creating new issues. (Issues API)
      • Step 5.3: Create a new issue with the value of the issue_title specified in the Pre-request Script. Save issue_id for the asset you just created. (Issues API)
      • Step 5.4: Associate the issue of Step 4.3 with the asset created in Step 3. (Assets API)
    • Step 5: Delete Asset Relationships
      • Step 5.1: Get relationship of the asset created in Step 3, save relationship ids to asset_relationship_id_array. (Assets API)
      • Step 5.2: Dissociate relationships of the asset created in Step 3. (Assets API)
    • Step 6: Delete (deactivate) the asset created in Step 3. (Assets API)
  • Retrieve BIM 360 Assets Data: It contains a set of Postman scripts demonstrating how to fetch your complete set of BIM 360 Asset data and metadata. This collection can be for the entirety of your Asset data or filtered to a subset of Asset data.

    • Step 1: Fetch all available assets in your project. (Assets API)
    • Step 2: Fetch all available assets categories in your project. (Assets API)
    • Step 3: Fetch Status Sets And Asset Statuses
      • Step 3.1: Fetch all available Asset Status Sets in your project. (Assets API)
      • Step 3.2: Fetch all available Asset Status in your project. (Assets API)
    • Step 4: Fetch Asset Status Sets assign to the ids of categories given in the POST body. (Assets API)
    • Step 5: Fetch all available Asset Custom Attributes in your project. (Assets API)
    • Step 6: Fetch all available Custom Attributes assign to the given id of the category. (Assets API)
    • Step 7: Fetch Locations (Not available yet since Locations API hasn't been released)
    • Step 8: Fetch all available relationship data of the Assets data in your project (Relationships API)

Further Reading

Automate Workflow with Postman Collection Runner

With the help of the Postman Collection Runner, you can actually automate the workflow, it helps you to quick verify your workflow with BIM 360 Assets API, or to do automation test to catch all the API issues|regresions

bim360 workflow automation test

Please watch the Video for the detail workflow, or follow the steps:

Tutorials about workflow

Note: The collection will first create an asset category, then create an asset and assign the asset to the category, after that, create a custom attribute, and then attach the custom attribute to the category, and assign a value of the custom attribute to that asset.

License

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

Written by

Eason Kang @yiskang, Forge Partner Development