Q. The BIM 360 Account I had for my development is expired. What can I do to extend it?
A. If your dev account is expired, but you still need it for your development purpose, you can send a request to:
bim360appsactivations@autodesk.com
with the title “BIM 360 Docs – API Activation Request”. When you do so, please include the email address of BIM 360 Account Admin, and explain that your account was expired and you want to extended it.
Update June 19, 2020: Rate Limits information is added to the developer portal now. e.g., for Data Management Rate Limits. Rate limits in other Forge API should be added near future as well.
Rate limiting is used to control amount of traffic sent or received by a network. For example, if you are using a certain API which is configured to allow 1000 requests per minute, your call will fail after hitting the limit, typically resulting 429 return code. This is a commonly used practice for a better flow of data and to increase security by mitigating attacks such as DoS.
Forge has rate limiting as well. When you are writing a code for scalable solution, you will need to take it into consideration; i.e., When you hit a limit, you will need to wait till given period has lapsed and retry. 429 response will contain “Retry-After” http header, which indicates the number of seconds after which the client can call again. Below is an example of response when hitting a limit:
Last updated: 10/24/2020
I receive inquiries about BIM 360 and API all the time. There are certain topics which pops up quite regularly. I have been thinking to have a page about them so that people can see what is known and what is potentially needed to report or raise as a wish. So here is it, below is the list of issues and wishes we are aware of. This is not meant to be an exhaustive list. I plan to add more here as we encounter new items. Of course, I will mark as resolved when a certain item is resolved.
If you have been using Field API’s endpoint: GET /fieldapi/checklists/v1/:id, you may be aware that it did not return “source” information; “source” field in response has been simply “{}”. This was because “source” was added after the API was written, there was an enhancement wish logged against it (CS-34452). The good news is that this has been implemented recently (June 3, 2019 to be exact). Now you can get this field value (y).
Continue reading “fieldapi/checklists/v1/:id Change in “source” Field in Response”
BIM 360 Project Home has a feature that allows you to customize its dashboard. The user can choose a “card” from a card library and add a pane within the main web page of Project Home, which represents the entrance to your app much like iframe does in HTML.
Continue reading “BIM 360 Project Home: Card Library and Partner Apps”
As I’m preparing for a class at BiLT ANZ 2019 conference in Melbourne, I was putting together a list of learning materials for Design Automation, specifically with Revit users in mind. Design Automation for Revit (or “DA for Revit” in short here) is currently in public beta. Anybody can give it a try.
That said, for any serious development, you do need Revit installed on your desktop as after all, you will be running Revit add-ins in the cloud. If you want to learn how Design Automation works and get a feel of it by running code samples, it is possible to try out without having a desktop version of Revit.
To start with, let me list learning materials below:
As described in this blog, there has been a change in API to access data stored in BIM 360 Docs in European data center. If you have customers in Europe, you most likely want to test your apps in European environment. (Please note that BIM 360 Docs in European region may have limited features compared with the version that is hosted in U.S. data center as typically new features are released in the U.S. first.)
If you wish to have a test environment in European region, please request for a free BIM 360 Docs account as below.
Continue reading “BIM 360 Docs Development Account for European Region”
Attention BIM 360 Issues API developers –
Around AU (Autodesk University) time frame, there will be a semantic change introduced to the current BIM 360 Issues API. Field Issues and Document Issues will be consolidated as a single set of Issues; i.e., Field Issues will include Document Issues, and Document Issues will be deprecated.
This change is expected to take place alongside of product’s Issues data migration and UI changes. At AU, you will hear the product team announcing the change and describe the detail. This is a part of enhancement that BIM 360 team is making in the effort to expand Issues functionalities to other modules and to provide a consistent, unified Issues feature.
Hard to believe, but AU/DevCon Las Vegas, the biggest annual event by Autodesk, is less than two weeks away now. Our marketing team is busy pushing for the number of registrations while various product teams are working hard trying to push the new features out by AU. Our team including myself is busy reviewing new APIs and writing samples with APIs which are still hot in the oven.
I myself is speaking at one DevCon class about BIM 360 API on Monday, co-presenting with Xiaodong Liang and Augusto Goncalves:
Update June 15, 2019: Design Automation for Revit (DA4R for short) is currently in public beta. I’ve created a designated page for DA4R, which I intend to update as we go along. Please refer to it for further development.
As of this writing (6/20/2018), Design Automation for Revit (DA4R) is in private beta. It’s not publicly available. But we receive inquiries quite frequently. So I’m putting together a list of available materials to learn about DA4R. I intend to update this page as more information become available.
To use DA4R, you will need to know both worlds: Revit addin as desktop application, and Forge and/or Web programming. If you are not familiar with both, you may start looking at them to be ready when DA4R is.
