Q: Can you tell us a bit about your journey in getting involved with Revit API
My journey to the API was that I was the Quality Assurance Manager for Revit Architecture and Revit Structure for several years, starting when Revit was a small startup company with no customers and before our first release. I always tried to use scripting techniques with languages like Perl to improve our testing efficiency and completeness, and was excited when a member of our QA team was able to use the API to greatly expand the range of programmatic testing that could be done far beyond what could be tested if we were limited to manual interaction through the user interface.
In 2008 I transferred to a software development position in the API group and have been helping design and test new API functionality (such as the Family Editor API and Conceptual Massing API in the 2010 release), teach other Autodesk employees about the API, work with the writers for the API documentation, design and write API samples, and more.
‘ I think an interesting future for this might be what www.guru.com has been doing to match freelance developers with potential customers. Not every Revit user will want to code their own Revit API applications, but having access to a worldwide network of developers interested in doing big and small projects might work well for both groups .’ – Harry Mattison (May 2009)
Here is a great Revit API summary compiled by myself with the endless help and patience from Harry Mattison & Guy Robinson.